Keep one catalogue of agent tools

Review by

2027-04-30

How to do it

Experimental. This rests on a draft or a proposal, not a standard, so recheck it by the review date. Serve an AI Catalog as application/ai-catalog+json with specVersion and entries. Give each entry an identifier, a type (the media type of what it points to) and a url. Leave out an entry's displayName when the card it points to has its own name. Link it with rel="ai-catalog". The format is a draft from the A2A and MCP communities, under the Linux Foundation. For an API, also follow Make the API easy for agents to find.

Examples

JSON example

{
  "specVersion": "1.0",
  "host": { "displayName": "Example Co.", "identifier": "example.com" },
  "entries": [
    {
      "identifier": "urn:air:example.com:mcp:bookings",
      "type": "application/mcp-server-card+json",
      "url": "https://example.com/mcp/server-card"
    },
    {
      "identifier": "urn:air:example.com:a2a:helper",
      "type": "application/a2a-agent-card+json",
      "url": "https://example.com/.well-known/agent-card.json"
    }
  ]
}

HTML example

<link rel="ai-catalog" href="/.well-known/ai-catalog.json">

How to check

The catalog parses as JSON. Every entry's URL answers 200 with the media type named in its type. Every page has the rel="ai-catalog" link.

Related rules

• AGT-62 Publish an agent card in Agents as users
• API-49 Make the API easy for agents to find in API design