Google A2A

Executive Summary

A2A (Agent2Agent) is an open protocol for enabling communication between opaque AI agents — agents that don't share internal state, memory, or tools. Launched by Google in April 2025 and donated to the Linux Foundation two months later, it has become the leading standard for agent interoperability, with 150+ supporting organizations and SDKs in five languages. ^{[1] [2]} In March 2026 the project shipped v1.0, its first stable, production-ready release. ^[3]

The protocol's core insight: agents should interact as peers, not as tools. A2A treats each agent as an opaque service that advertises capabilities via Agent Cards, accepts tasks, and returns results — without requiring the caller to know anything about the agent's internal architecture.

---

Product Overview

A2A defines how agents discover, communicate, and collaborate over standard web infrastructure. ^[4]

Key Capabilities

Protocol Stack

How It Works

Client Agent                         Server Agent
     │                                    │
     │── GET /.well-known/agent-card.json ►│  (Discovery)
     │◄── Agent Card ────────────────────│
     │                                    │
     │── tasks/send ────────────────────►│  (Create task)
     │◄── Task (submitted/working) ──────│
     │                                    │
     │── tasks/get ─────────────────────►│  (Poll or SSE)
     │◄── Task (completed + artifacts) ──│

---

Technical Architecture

A2A is designed as a thin coordination layer, not a framework. ^[4]

v0.3 Additions (July 2025)

• gRPC support for high-performance agent communication
• Signed security cards for enterprise trust verification
• Extended Python SDK with richer type support
• Agentspace integration for Google Cloud agent marketplace ^[5]

v1.0 — Stable Release (March 2026)

• Signed Agent Cards — cryptographic signatures let a receiving agent verify a card was issued by the domain owner
• Multi-tenancy — a single endpoint can host multiple agents, so SaaS providers can serve different agents per tenant
• Multi-protocol bindings — the same logical agent can be exposed over JSON-RPC, gRPC, and HTTP/REST
• Proto-first spec — spec/a2a.proto becomes the normative source of truth
• Breaking changes — the kind discriminator was removed and the extended Agent Card endpoint relocated, requiring migration from 0.x ^{[3] [4]}

---

Strengths

• Industry momentum — 150+ supporting organizations with integrations across Google, Microsoft, and AWS platforms; the closest thing to a standard the space has ^[6]
• Stable 1.0 — Production-ready spec as of March 2026, with enterprise production deployments reported in year one ^{[3] [6]}
• Neutral governance — Linux Foundation stewardship plus Google's resources and cloud integration (Agentspace, Vertex AI) ^[2]
• Framework-agnostic — Works with any agent framework (LangGraph, CrewAI, AutoGen, custom)
• Multi-language SDKs — Python, Go, JS, Java, .NET covers most enterprise stacks
• Complementary to MCP — Clear separation of concerns; doesn't compete with tool protocols
• Enterprise security — OAuth, signed cards, and auth delegation from day one
• DeepLearning.AI course — Structured learning path accelerates adoption

---

Cautions

• 1.0 migration cost — v1.0 includes breaking changes from 0.x (removed kind discriminator, relocated extended Agent Card), so early adopters must migrate ^[4]
• Enterprise-first complexity — The spec optimizes for enterprise orchestration over indie developer experience; getting started is heavier than MCP
• Stateless bias — Task-based model is simpler but less suited to long-lived multi-party transactions
• No built-in trust/reputation — Signed Agent Cards verify issuer identity, but there's no protocol-level trust scoring
• Discovery is basic — Agent Cards are static JSON; no dynamic marketplace or semantic matching
• Adoption depth still uneven — The Linux Foundation cites enterprise production use, but 150+ "supporting" organizations still doesn't mean 150+ production deployments ^[6]
• Competing protocols — ACP, ANP, and Summoner offer different trade-offs

---

What Developers Say

From the Hacker News launch discussion (April 2025): ^[7]

"It's frustratingly difficult to see what these (A2A and MCP) protocols actually look like. All I want is a simple example conversation that includes the actual LLM outputs used to trigger a call and the JSON that goes over the wire." — zellyn

"I think they are trying to ride the MCP hype as well with their own implementation that is also meh... Obviously the end game is control over a standard which can act as a strategic tool for boosting valuations or even better product positioning." — pdp

"Great, another Agent 2 Agent protocol. One more of those and we'll have a complete set! OK, I'm being a little bit facetious. But there has been an awful lot of work in this space... Going back to FIPA, KQML, DAML+OIL, etc." — mindcrime

These are launch-era reactions; the Linux Foundation handoff and the v1.0 release addressed the governance concern directly, though the documentation-clarity complaint still echoes in newer discussions. Little verbatim developer commentary on v1.0 itself has surfaced yet as of June 2026.

---

Pricing & Licensing

---

Competitive Positioning

---

Ideal Customer Profile

Best fit:

• Enterprises building multi-vendor agent ecosystems
• Teams integrating agents from different frameworks
• Google Cloud customers wanting Agentspace integration
• Organizations needing industry-standard agent interoperability

Poor fit:

• Single-agent applications
• Teams needing deep cross-organizational trust and state management
• Decentralized/permissionless agent networks
• Indie developers who just need tool access — MCP is the simpler on-ramp

---

Viability Assessment

---

Bottom Line

A2A is the front-runner for agent-to-agent interoperability, and the question mark over it is gone: v1.0 shipped in March 2026 as a stable, production-ready spec under neutral Linux Foundation governance. ^[3] The combination of multi-language SDKs, broad industry support, and integration into Google, Microsoft, and AWS platforms gives it the strongest network effects of any protocol in the space. ^[6] The task-based model is pragmatic — simple enough to adopt, flexible enough for most use cases.

Recommended for: Any team building multi-agent systems that need to interoperate across frameworks or organizations.

Not recommended for: Teams needing durable cross-organizational state management (look at Summoner) or decentralized identity (look at ANP).

Outlook: A2A is on track to become the HTTP of agent communication — good enough for most use cases, with specialized protocols (Summoner, ANP) filling gaps for advanced scenarios. With 1.0 landed, the open question shifts from "will it stabilize?" to how deep production adoption runs beyond the headline 150+ supporter count.

---

Research by Ry Walker Research • methodology