Protocols

Each protocol record explains its documented scope, limitations and version status, with an editorial implementation checklist. These are source-based explanations, not interoperability tests.

Source-linked research and editorial guidance. Capabilities are not independently tested unless a profile explicitly includes a reproducible test record. Sources checked November 13, 2026.

Compare protocols

13 protocol records

Agent Client Protocol

Coding-agent/editor connectionLifecycle noteAgent Client Protocol connects coding agents with editors or IDEs. Record which agent, editor and protocol release were documented or tested together.

Agent Commerce Protocol (Virtuals)

Agent service commerceVirtuals describes ACP as a framework for agreements and commerce among agents and as a reference implementation of proposed ERC-8183. Keep the deployed implementation and draft interface distinct.

Agent Communication Protocol (IBM BeeAI)

Historical interoperabilityLifecycle noteIBM describes this ACP as historical work moving into A2A. Preserve a legacy record so older articles and repositories can be understood in context.

Agent Payments Protocol

Payment authorizationLifecycle noteAP2 describes payment mandates and verifiable credentials for agent commerce. Model the authorization evidence separately from the payment service and its settlement mechanism.

Agent Skills

Reusable instructionsA portable skill package groups instructions and optional resources around SKILL.md. Record the skill directory, revision and dependencies separately from the agent that loads it.

Agent2Agent

Agent-to-agent interactionA2A describes agent communication and task coordination. Agent Cards advertise identity, skills and interaction requirements. Store the card and each supported interface as evidence.

Agentic Commerce Protocol (OpenAI and Stripe)

Merchant checkoutLifecycle noteThis ACP is the OpenAI and Stripe commerce protocol. Its scope concerns interactions among buyers, agents and businesses, including checkout and delegated payments.

ERC-8004 Trustless Agents

Identity and reputationDraftERC-8004 proposes registries for agent identity, reputation and validation. The inspected proposal is marked Draft; payments are outside its stated scope.

ERC-8183 Agentic Commerce

Job escrowDraftERC-8183 proposes a job escrow interface with client, provider and evaluator roles. The evaluator accepts or rejects work and may be the client. The inspected proposal is Draft.

Machine Payments Protocol

Machine paymentsMPP describes web payments with SDKs, service discovery and extensible payment methods. Separate the protocol, service catalog and individual paid endpoints.

Model Context Protocol

Tools and contextLifecycle noteMCP connects AI applications with external capabilities and context. In this atlas, an MCP server is a separate entity from its operator and the products it exposes.

Universal Commerce Protocol

Commerce lifecycleUCP supplies commerce building blocks covering discovery, checkout and later interactions. Treat a merchant implementation as a separate record with its own supported capabilities.

x402

HTTP resource paymentsx402 describes payment for internet resources through an HTTP payment flow. Distinguish the resource seller, client, facilitator and discovery catalog.