Protocols (29)
Open protocols and standards for agents and agent interoperability.
Machine-readable: /api/protocols.json.
- AG-UI (Agent-User Interaction Protocol)
Open, lightweight, event-based protocol that standardizes how AI agents connect to user-facing frontend applications.
- Agent Client Protocol (ACP)
Protocol for connecting any code editor to any coding agent, standardizing editor-agent communication.
- Agent Plugins
Vendor-neutral standard (v1.0.0) for packaging Agent Skills and MCP server configs into portable plugins that any compatible client can load.
- Agent Skills Discovery RFC (beta)
Cloudflare's draft for publishing Agent Skills at /.well-known/agent-skills/, with an index.json listing each skill and a SHA-256 digest.
- Agent Skills Specification
Open format for packaging agent capabilities as folders with a SKILL.md (YAML frontmatter + instructions) plus optional scripts and resources.
- Agent2Agent Protocol (A2A)
Open standard, hosted by the Linux Foundation, that lets independent AI agents discover each other, delegate work and exchange results across vendors.
- AGENTS.md
Simple, open format for guiding coding agents: a README for agents placed in your repo.
- AI Catalog (beta)
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.
- Arazzo Specification
OpenAPI Initiative spec for describing deterministic sequences of API calls and their dependencies as workflows.
- Cross App Access (ID-JAG) (beta)
IETF OAuth draft (Identity Assertion JWT Authorization Grant) letting an app use an SSO identity assertion, via the trusted IdP, to get access tokens for a third-party API.
- Dogwood
Open policy language for governing AI agents and their tools: Cedar-style permit/forbid rules plus temporal conditions over an agent's recent actions.
- ERC-8004: Trustless Agents (unknown)
Ethereum standard proposal for discovering agents and establishing trust through reputation and validation.
- llms.txt
Proposal to standardize a /llms.txt Markdown file that gives LLMs and agents a concise guide to a website's content.
- MCP Authorization (OAuth 2.1 for MCP)
The MCP specification's transport-level authorization flow for HTTP-based MCP servers, based on a subset of OAuth 2.1 and related RFCs.
- MCP Authorization Extensions (ext-auth)
Official repo of optional, additive extensions to MCP authorization, such as Enterprise-Managed Authorization (stable) and OAuth Client Credentials (draft).
- MCP Server Cards
MCP extension (SEP-2127, Final) defining a static JSON card that describes a remote MCP server's identity and transport endpoints so clients can find and connect to it.
- Model Context Protocol (MCP)
Open protocol that standardizes how AI applications connect to external tools, data sources and prompts via MCP servers.
- NLWeb
Open protocols and reference implementation for natural-language interfaces to websites, using Schema.org/RSS and natively supporting MCP.
- OAuth Client ID Metadata Document (CIMD) (beta)
IETF OAuth draft letting a client identify itself with a URL as its client_id, pointing to a metadata document, without prior dynamic registration.
- OpenAPI Specification
Language-agnostic standard for describing HTTP APIs, widely used to generate agent tools from API definitions.
- OpenID Connect CIBA (Client-Initiated Backchannel Authentication)
OpenID flow where a relying party obtains tokens after the user authenticates and consents on a separate device, with no redirects through the user's browser.
- OpenTelemetry GenAI Semantic Conventions
OpenTelemetry conventions for spans, metrics and events emitted by GenAI clients, MCP and model providers, for interoperable agent observability.
- RFC 8693: OAuth 2.0 Token Exchange
IETF Proposed Standard for exchanging one security token for another at the token endpoint, enabling delegation and impersonation flows.
- RFC 8707: Resource Indicators for OAuth 2.0
IETF Proposed Standard adding a `resource` parameter so a client can tell the authorization server which protected resource a token is meant for (audience binding).
- 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.
- 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.
- Web Bot Auth (beta)
IETF draft architecture for identifying automated traffic (bots and agents) by cryptographically signing HTTP requests with HTTP Message Signatures.
- WebMCP (beta)
Proposed web API letting sites expose JavaScript functions or HTML forms as tools with natural-language descriptions and schemas for in-browser AI agents.
- x402
Open standard for internet-native payments built on HTTP 402, letting APIs and agents pay per request across crypto and fiat networks.