Orbit: Agent communication and tooling
A2A (Agent2Agent)
An open protocol for agents to find each other through Agent Cards and hand off tasks over JSON-RPC, gRPC or HTTP bindings.
- Steward
- A2A Project at the Linux Foundation
- Status
- Live
- Primary source
- Agent2Agent (A2A) Protocol Specification (external link)
What it is
gives an a published , a JSON document that describes its skills, endpoints and security schemes, plus a task model that a client agent drives across a network boundary. Tasks carry messages and artifacts and move through states such as input-required. The public Agent Card is served at /.well-known/agent-card.json, and the specification separates the application protocol from its JSON-RPC, gRPC and HTTP transport bindings. Source [1]
A2A is often compared with : MCP connects one application to the tools and data it uses, while A2A connects agents to other agents. Source [2]
Status
is live and published as a Linux Foundation project. Source [1] On 2025-08-29 the LF AI and Data Foundation announced that IBM’s Communication Protocol (not OpenAI’s ACP) was joining forces with A2A. Source [3]
How it relates to the eight
In the payments orbit is a transport and a container for .
- AP2 calls itself an open extension for A2A (and for and UCP), and its Python samples run merchant, credentials provider and payment processor agents that talk over A2A. Source [4, 5]
- For x402, the
a2a-x402repository defines the x402 Payments Extension v0.1 with the extension URIhttps://github.com/google-a2a/a2a-x402/v0.1and the payment statespayment-required,payment-submittedandpayment-completed. Source [6, 7] x402 v2 carries a matching A2A transport that signals payment with the task stateinput-requiredandx402.payment.statusmetadata. Source [8] - UCP defines an A2A binding for its checkout , and businesses that support it publish an endpoint. Source [9]
- ERC-8004 registration files can list an
A2Aservice that points to an agent card, and feedback entries can reference A2A skills,contextIdandtaskId. Source [10]
No direct A2A binding was found in the cloned specs of ACP, MPP, or Mastercard Pay.
Relations at a glance
| Protocol | Relation | Note |
|---|---|---|
| AP2 | Complements | AP2 describes itself as an open extension for A2A, and its samples run merchant, credentials provider and processor agents over A2A. |
| x402 | Complements | The a2a-x402 extension v0.1 and the x402 A2A transport carry x402 payment states inside A2A task messages. |
| UCP | Complements | UCP's checkout capability has an A2A binding; businesses using it publish an agent card endpoint. |
| ERC-8004: Trustless Agents | Compatible with | ERC-8004 registration files can point to an A2A agent card, and feedback can reference A2A skills, contextId and taskId. |
Sources
- Agent2Agent (A2A) Protocol Specification (external link)
- A survey of agent interoperability protocols: MCP, ACP, A2A and ANP (external link)
- ACP Joins Forces with A2A (external link)
- AP2 - Agent Payments Protocol Documentation (external link)
- AP2 repository (README, METADATA, LICENSE) at e1ea56d (external link)
- A2A Protocol: x402 Payments Extension v0.1 (external link)
- a2a-x402 repository (A2A x402 extension) (external link)
- x402 A2A transport (V2) (external link)
- Checkout A2A binding (v2026-08-25) (external link)
- ERC-8004: Trustless Agents (specification source, ERCS/erc-8004.md) (external link)