Agent2Agent Protocol (A2A)
A2A, the Linux Foundation protocol for communication between independent AI agents: agent cards, tasks, bindings, governance and commerce uses.
In short: Agent2Agent (A2A) is an open protocol that lets AI agents built by different companies on different frameworks find each other, delegate tasks and exchange results. Google introduced it in April 2025 and contributed it to the Linux Foundation in June 2025. Version 1.0 was released in 2026. In commerce, A2A is the transport for agent-to-agent shopping and payment flows, and AP2 and UCP both build on it.
Where A2A fits
MCP connects an agent to tools: functions that do what they’re told. A2A connects an agent to other agents: independent systems that have their own reasoning, may take time, may ask follow-up questions and don’t expose how they work inside. The two are designed to be used together. A shopping agent might use MCP to call a catalog API and A2A to negotiate with a merchant’s sales agent.
A2A is built on familiar web standards: HTTPS, JSON, OAuth and OpenID Connect. Its design principle is that agents work together without sharing their internal memory, tools or prompts. They are “opaque” to each other.
Core concepts
Agent Card
An Agent Card is a JSON document an A2A server publishes to describe itself. By convention it lives at a well-known URL on the agent’s domain. It includes:
- identity: name, description, provider
- the service endpoint(s) and supported protocol bindings
- skills: what the agent can do, with descriptions and example inputs
- supported capabilities, such as streaming and push notifications
- required authentication schemes
- declared extensions
Version 1.0 supports signed Agent Cards. The card is cryptographically signed so a client can check that it really comes from the stated provider and hasn’t been altered. Servers can also offer an extended card with more detail to authenticated clients only.
Tasks, messages and artifacts
| Object | Role |
|---|---|
| Task | The unit of work, with an ID, a status and a history. States include submitted, working, input-required, auth-required, completed, failed, canceled and rejected. |
| Message | One turn of communication from the user side or the agent side, grouped by a context ID |
| Part | A piece of content inside a message or artifact: text, a file or structured data |
| Artifact | An output the task produces, such as a quote, a cart or a booking confirmation |
The input-required and auth-required states matter for commerce. They let a merchant agent pause and ask the shopping agent, and through it the user, for a size choice, a shipping address or an authentication step.
Bindings and delivery
Version 1.0 defines three equivalent bindings: JSON-RPC 2.0 over HTTPS, gRPC, and HTTP+JSON (REST). Protocol Buffers are the normative definition. Long-running work can be followed through streaming or through push notifications sent as webhooks to an endpoint the client registers. Supported authentication includes API keys, HTTP bearer tokens, OAuth 2.0, OpenID Connect and mutual TLS.
Extensions
A2A has a formal extension mechanism. Agents declare extensions by URI, can mark them as required, and negotiate support. The commerce protocols use this mechanism.
Governance and status
- April 2025: Google announces A2A with more than 50 technology partners.
- June 23, 2025: the Linux Foundation launches the A2A project. Founding members are Google, AWS, Cisco, Microsoft, Salesforce, SAP and ServiceNow, with more than 100 supporting companies.
- 2026: version 1.0 is released. It adds signed agent cards, multi-tenancy, updated security flows and a migration path from the 0.x versions. Official SDKs cover Python, TypeScript, Java, Go and C#. Google’s one-year review reported interoperability across agent frameworks including Google’s ADK, LangGraph, AG2 and CrewAI.
A2A is a Linux Foundation project in its own right, separate from the Agentic AI Foundation that hosts MCP.
Commerce use cases
Payment authorization: AP2
The Agent Payments Protocol was first published as an A2A extension. Its signed mandates travel between the shopping agent, the merchant, the credentials provider and the payment processor as A2A messages and artifacts. Google describes AP2, UCP and A2UI (an agent-to-user-interface spec) as built on A2A’s extension model.
Checkout: UCP
The Universal Commerce Protocol lists A2A as one of its transports, next to REST and MCP. A business that runs its own agent can offer UCP capabilities, such as checkout, cart and identity linking, through that agent rather than through plain APIs.
Typical scenarios
- Merchant agents. Retailers and brands deploy sales or support agents that can answer detailed product questions, apply promotions or set up a custom order. A consumer’s shopping agent talks to them over A2A instead of scraping pages.
- Multi-agent purchases. A travel or event agent coordinates with separate agents for flights, lodging and tickets, each holding its own inventory and rules.
- Procurement. A buyer-side agent requests quotes from several supplier agents, compares the returned artifacts and asks the user for approval.
- Post-purchase. Returns, exchanges and order status can be handled as tasks with a merchant’s service agent.
Limits
A2A defines how agents talk, not what they say about commerce. Product, cart and order data need a shared schema, such as UCP’s. Payment approval needs AP2 or an equivalent. Signed agent cards prove who publishes an agent, but merchants still need policies on which agents to trust. On the open web, agents usually still reach merchants over HTTP, and Web Bot Auth covers their identity there. Most consumer shopping in 2026 still runs through agents calling APIs and MCP servers directly. Merchant-run A2A agents are less common.
Sources
- Announcing the Agent2Agent Protocol (A2A) — Google Developers Blog
- Linux Foundation launches the Agent2Agent Protocol project — Linux Foundation
- A2A Protocol Specification — a2a-protocol.org
- A year of open collaboration: Celebrating the anniversary of A2A — Google Open Source Blog
- Announcing Agent Payments Protocol (AP2) — Google Cloud Blog
- Under the Hood: Universal Commerce Protocol (UCP) — Google Developers Blog