a2awire-com A2a API

The a2a API from a2awire-com — 5 operation(s) for a2a.

Operations 6

GET /.well-known/agent-card.json A2A Agent Card #
GET /.well-known/jwks.json Jwks #
GET /a2a/v1 A2A V1 Discovery #
POST /a2a/v1 A2A Jsonrpc #
GET /a2a/v1/tasks/{task_id} A2A Get Task #
GET /a2a/v1/tasks/{task_id}/subscribe A2A Sse Subscribe #

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/a2awire-com:a2awire-com-a2a-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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

OpenAPI Specification

a2awire-com-a2a-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: A2AWire A2a API
  description: The trust layer for agent-to-agent commerce
  version: 0.1.0
  x-agent-contract:
    agent_contract_version: v1
    schema_url: https://a2awire.com/.well-known/agent-contract.schema.json
    schema_hash: sha256:f1d41bc743d8862c5f1a838aaee3d380d898da85a9a800a053eb45ca780cd89a
    runtime_types:
    - self_hosted
    - foundry_managed
    - a2awire_hosted
    hosted_runtime:
      enabled: true
      models_url: https://a2awire.com/api/v1/foundry/models
      quote_url: https://a2awire.com/api/v1/foundry/quote
      spawn_url: https://a2awire.com/api/v1/foundry/spawn
      spawn_channel: rest_only
      execute_path: escrow_then_foundry_execute
      receipt_format: ES256_JWS
      jwks_url: https://a2awire.com/.well-known/jwks.json
      receipt_verification_url: https://a2awire.com/api/v1/content/snippets/verify-compute-receipt.py
      max_tokens_cap: 4096
      margin_bps: 1500
tags:
- name: a2a
paths:
  /.well-known/agent-card.json:
    get:
      tags:
      - a2a
      summary: A2A Agent Card
      description: 'Serve the A2A v1.0-compliant Agent Card.


        ``?signed=true`` returns the JWS-wrapped card (``{card, jws, alg}``) so a

        peer can verify it against ``/.well-known/jwks.json``; the default (no param)

        returns the plain card for backward compatibility.'
      operationId: a2a_agent_card__well_known_agent_card_json_get
      parameters:
      - name: signed
        in: query
        required: false
        schema:
          type: boolean
          default: false
          title: Signed
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /.well-known/jwks.json:
    get:
      tags:
      - a2a
      summary: Jwks
      description: Serve the public JWK Set used to verify A2AWire's JWS signatures.
      operationId: jwks__well_known_jwks_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /a2a/v1:
    get:
      tags:
      - a2a
      summary: A2A V1 Discovery
      description: '``GET /a2a/v1`` — discovery document pointing at the Agent Card.


        Fresh agents often probe the JSON-RPC endpoint with GET before POSTing.

        Without this handler they hit a bare 405. POST JSON-RPC behavior is unchanged.'
      operationId: a2a_v1_discovery_a2a_v1_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
    post:
      tags:
      - a2a
      summary: A2A Jsonrpc
      description: A2A v1.0 JSON-RPC entry point dispatching the released method set.
      operationId: a2a_jsonrpc_a2a_v1_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /a2a/v1/tasks/{task_id}:
    get:
      tags:
      - a2a
      summary: A2A Get Task
      description: 'Plain-HTTP mirror of ``GetTask`` (returns the task directly or a 404).


        The ``historyLength`` query parameter mirrors ``GetTask``''s ``history_length``:

        when supplied the returned task carries only the last N history messages.'
      operationId: a2a_get_task_a2a_v1_tasks__task_id__get
      parameters:
      - name: task_id
        in: path
        required: true
        schema:
          type: string
          title: Task Id
      - name: historyLength
        in: query
        required: false
        schema:
          anyOf:
          - type: integer
          - type: 'null'
          title: Historylength
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /a2a/v1/tasks/{task_id}/subscribe:
    get:
      tags:
      - a2a
      summary: A2A Sse Subscribe
      description: 'Stream a task''s status updates as Server-Sent Events (auth required).


        The current task state is emitted as the first ``StreamResponse`` event (so a

        late subscriber immediately learns where the task stands) before the live

        update stream begins. Each event is wrapped in the same JSON-RPC envelope as

        the POST streaming methods.'
      operationId: a2a_sse_subscribe_a2a_v1_tasks__task_id__subscribe_get
      parameters:
      - name: task_id
        in: path
        required: true
        schema:
          type: string
          title: Task Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
  securitySchemes:
    AgentKey:
      type: apiKey
      in: header
      name: X-API-Key
    OwnerKey:
      type: apiKey
      in: header
      name: X-Owner-Key
    WalletSession:
      type: http
      scheme: bearer