EU Compliance Toolkit .well Known API

The .well Known API from EU Compliance Toolkit — 2 operation(s) for .well known.

Documentation GitHub OpenAPI

Operations 2

0 of 2 operations are conformant: apis.io called them with no credentials and the responses matched this contract; 2 more answered but could not be checked against a schema. Checked 2026-11-12. how this works · status file

GET /.well-known/x402 Well Known X402 observed #

GET /.well-known/agent-card.json Agent Card observed #

Specifications

⚙

OpenAPI

https://artifacts.apis.io/eucompliance-tools/openapi/eucompliance-tools-well-known-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/eucompliance-tools:eucompliance-tools-well-known-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Agent Decision & Evidence Layer .well Known API
  version: 1.7.0
  description: Public HTTP and x402 interfaces for agent infrastructure, market decisions, AgentLLM inference, EU compliance and US import-readiness. MCP tool errors and HTTP 4xx/5xx responses are not settled; a domain result returned with HTTP 200 is a delivered paid result. Signed results expose source evidence and freshness where applicable.
servers:
- url: https://api.eucompliance.tools
tags:
- name: .well Known
paths:
  /.well-known/x402:
    get:
      summary: Well Known X402
      description: 'Standard-Auffindungspfad fuer x402-Agenten.


        Wurde 686-mal angefragt und gab 404 zurueck - Agenten, die dem Protokoll

        folgen, haben unsere Dienste dadurch nie gesehen. Der Inhalt ist derselbe

        wie unter /agents.json, nur am erwarteten Ort.'
      operationId: well_known_x402__well_known_x402_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '400':
          description: Invalid input; no paid result delivered
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MachineError'
        '422':
          description: Request schema validation failed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MachineError'
        '503':
          description: Critical upstream evidence unavailable; retry later
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MachineError'
      tags:
      - .well Known
  /.well-known/agent-card.json:
    get:
      summary: Agent Card
      operationId: agent_card__well_known_agent_card_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '400':
          description: Invalid input; no paid result delivered
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MachineError'
        '422':
          description: Request schema validation failed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MachineError'
        '503':
          description: Critical upstream evidence unavailable; retry later
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MachineError'
      tags:
      - .well Known
components:
  schemas:
    MachineError:
      type: object
      additionalProperties: true
      properties:
        error: {}
        detail: {}
        charged:
          type: boolean