Agents Addressing Agents: A2A, ACP and the Interoperability Ledger

More than 150 organizations, 22,000-plus GitHub stars and five production-ready SDK languages: that was the Linux Foundation’s tally for the A2A protocol, Agent2Agent in full, on April 9, 2026, one year after Google launched it with about 50 partners. Luca Muscariello, a distinguished engineer at Cisco, said in the same release that “A2A has emerged as the syntactic layer that makes agent-to-agent communication reliable and interoperable.” The claim contains a hierarchy worth taking seriously. A syntactic layer settles how agents address one another; it leaves open whether they should, which is a question the Google and MIT scaling study answered with numbers in December 2025. This ledger records the A2A protocol’s dated adoption curve, separates the three protocols that share the ACP acronym, compares seven specifications for agent interoperability by scope and steward, and prices the coordination costs that sit beneath every one of them.

A2A Protocol Timeline: From 50 Partners to 150 Organizations in Production

Google announced A2A in April 2025 with more than 50 technology partners and a framing that has survived every revision since: MCP connects agents to tools, A2A connects agents to agents. On June 23, 2025, Google Cloud donated the specification to the Linux Foundation with 100-plus supporting companies, among them Microsoft, AWS, Cisco, Salesforce and SAP. Version 0.3 arrived on July 31, 2025, adding gRPC transport, signed Agent Cards and extended client support in the Python SDK, according to the Google Cloud post by Rao Surapaneni and Philip Stephens. By April 9, 2026, the foundation’s release counted 150-plus organizations, 22,000-plus stars, SDKs in Python, JavaScript, Java, Go and .NET, and version 1.0 as the first stable specification, with support landing in Microsoft Azure AI Foundry, Copilot Studio, Amazon Bedrock AgentCore Runtime, LangGraph and CrewAI.

Cloud Next added a wrinkle. Two version numbers circulate for the same month: the foundation’s April 9 release named 1.0 the first stable specification, while The Next Web’s April 22, 2026, report described the protocol as production-grade at version 1.2, with cryptographically signed Agent Cards for domain verification and 150 organizations routing real tasks between agents built on different platforms, and placed governance under the Linux Foundation’s Agentic AI Foundation, the directed fund that also houses MCP. Both are recorded here. Thomas Kurian’s advice to the conference, to “pick a few important projects and do them well,” reads as a caution against agent sprawl from the vendor most exposed to it.

MCP vs A2A: Two Layers With Two Adoption Curves

Adoption metrics reveal the difference between the layers. MCP’s maintainers reported 97 million monthly SDK downloads and 10,000 active servers on Dec. 9, 2025; A2A’s steward reported organizations and stars. Downloads count integrations against a consolidated client base, since a tool server written once reaches ChatGPT, Claude, Cursor, Gemini, Copilot and VS Code. Organizations count bilateral agreements. An A2A Agent Card is worthless until a second party’s agent reads it, so the protocol’s value grows with the square of participants and its early numbers stay small by construction. That is why the platform vendors matter more than the star count: Azure AI Foundry, Copilot Studio and AgentCore Runtime supply the counterparties that a bilateral protocol needs to bootstrap.

The two protocols also divide the trust problem. MCP’s security record concerns poisoned tools and path traversal inside a single agent’s boundary. A2A’s concerns who is on the other end of a task, which is why signed Agent Cards moved from version 0.3 to a headline feature by version 1.2 and why OWASP’s Top 10 for Agentic Applications, released Dec. 9, 2025, reserved a category, ASI07, for insecure inter-agent communication.

Three Protocols Called ACP: A Disambiguation

One acronym names three specifications with three purposes, and the collision costs buyers real time.

The Agentic Commerce Protocol from OpenAI and Stripe, open-sourced on Sept. 29, 2025, governs checkout inside a conversation: a Shared Payment Token scoped to a single merchant and cart total lets ChatGPT complete a purchase with Etsy live at launch and, per the Stripe release, more than 1 million Shopify merchants to follow. Its scope is a human buying through an agent.

Virtuals Protocol’s Agent Commerce Protocol governs agents buying from agents on-chain, through discovery, request, negotiation, escrow, evaluation and settlement. On Feb. 12, 2026, the company said that 18,000-plus agents had generated $470 million-plus in what it calls agentic GDP and that about $1 million a month flowed to agents selling through the protocol; all three figures are company claims.

IBM’s Agent Communication Protocol, a REST-based messaging specification with BeeAI as its reference implementation, occupied the same layer as A2A. Its project site now states that ACP is part of A2A under the Linux Foundation and offers a migration guide, which resolves the collision at the communication layer and leaves two commerce protocols holding the same three letters.

Agent Protocols Compared: Scope, Steward, Governance and Date

Two entries need dating care. AP2 arrived on Sept. 16, 2025, per the Google Cloud post by Stavan Parikh and Rao Surapaneni, with Intent and Cart Mandates signed as verifiable credentials, 60-plus organizations including Mastercard, American Express, PayPal, Adyen and Coinbase, and an A2A x402 extension built with Coinbase, the Ethereum Foundation and MetaMask. x402 launched on May 6, 2025, moved under a Linux Foundation-hosted foundation that Ripple joined in July 2026, crossed 100 million transactions in the first quarter of 2026 per Chainalysis figures reported by Crypto Briefing on June 3, 2026, and then saw on-chain settlement volume fall 93% year to date by Aug. 13, 2026, from roughly $800,000 a day in late 2025 to a seven-day average near $41,800, according to CoinDesk. Transaction counts and settlement value tell opposite stories about the same rail, and both belong in the ledger.

Coordination Costs: What the Google and MIT Evidence Says About Agent Handoffs

Interoperability has a price that the protocols themselves stay silent on. A team from Google Research, Google DeepMind and MIT led by Yubin Kim posted “Towards a Science of Scaling Agent Systems” to arXiv on Dec. 9, 2025, and revised it through April 8, 2026. The first version ran 180 controlled configurations with matched token budgets across four benchmarks; the third version reports 260 configurations across six. Its findings hold across versions. Centralized coordination improved performance by 80.9% on decomposable financial reasoning, while every multi-agent variant degraded sequential planning by 39% to 70%; independent agents amplified errors 17.2× as mistakes propagated with zero verification, against 4.4× under centralized coordination; and coordination yielded diminishing or negative returns once a single-agent baseline exceeded about 45%. The framework predicted the best architecture for 87% of held-out configurations. Tool-heavy tasks, such as 16-tool software engineering, paid a coordination overhead the authors quantified at a coefficient of −0.330.

Read against the protocol ledger, the study reorders priorities. A2A’s signed Agent Cards answer ASI07’s authentication question, and the study’s 4.4× figure says the verifier belongs at the center of the topology and away from its edges, which makes centralized orchestration the safer default for any handoff whose outputs feed a second agent. ASI08, OWASP’s cascading-fault category, is the 17.2× number restated as a risk entry. Adopting a wire format is cheap. Choosing a topology is where the money moves.

What to Watch

Three ledger entries will change first. The Linux Foundation’s next A2A count will show whether production use grows faster than membership, which is the metric that distinguishes a bilateral protocol from a logo wall. AP2’s Intent and Cart Mandates, signed as verifiable credentials, will meet their first disputed charge, and that adjudication will decide whether a mandate is a liability shield or a liability trail. x402’s transaction count and settlement volume will keep diverging until one of them describes the rail’s real use; Cloudflare’s Monetization Gateway, live since July 1, 2026, is the venue where that divergence gets resolved. Beneath all three sits the 45% threshold from the scaling study, because a protocol for agents addressing agents earns its keep on tasks where a single agent already falls short.