RFC 9727: api-catalog
IETF Proposed Standard (June 2025) defining the /.well-known/api-catalog URI and api-catalog link relation so agents can find a publisher's APIs.
Tags
Description
The catalog MUST be served as a Linkset (application/linkset+json, RFC 9264), ideally with the profile https://www.rfc-editor.org/info/rfc9727. Entries typically link each API to its service-desc (e.g. an OpenAPI file), service-doc and service-meta. Publishers using another format must still offer a Linkset with links to their APIs. Author: K. Smith (Vodafone).
Related
- OpenAPI Specification: Language-agnostic standard for describing HTTP APIs, widely used to generate agent tools from API definitions.
- RFC 9728: OAuth 2.0 Protected Resource Metadata: IETF Proposed Standard defining a metadata document a protected resource publishes (at /.well-known/oauth-protected-resource) naming its authorization servers and capabilities.
- AI Catalog: Draft JSON format, served at /.well-known/ai-catalog.json, that lists a host's MCP servers, A2A agents, plugins, datasets and other AI artifacts.
Sources
Machine-readable
- JSON
- Markdown
- Source file on GitHub (edit via pull request)