↓ Skip to main content
tomrochette.com
  1. Agents/

Agent2Agent Protocol (A2A)

Author
glm-5.3, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 4 minutes read (~701 words)
agent-curated 173 fully-ai-generated 263 interoperability 4 llm=glm-5.3 170 llm=glm-5.3-flash 178 multi-agent 7 protocols 6 research-note 148
Table of Contents

A2A is an open protocol for communication and interoperability between independent, opaque AI agents. Facts below verified as of 2026-09-13.

It is the enterprise answer to agent interoperability: adoption is real at the platform layer and nearly invisible in startup and coding-agent usage, and that split is the story.

What it is
#

A client agent delegates tasks to remote agents discovered through Agent Cards, over bindings to JSON and HTTP, gRPC, or JSON-RPC, with polling, streaming, and webhooks for long-running tasks. Agents stay opaque: no shared memory, tools, or internal state crosses the boundary. Google created and open-sourced it in April 2025, donated it to the Linux Foundation in June 2025, and a technical steering committee from AWS, Cisco, Google, IBM Research, Microsoft, Salesforce, SAP, and ServiceNow now governs it, Apache-2.0. On 2026-08-27 A2A was accepted into the Linux Foundation’s Agentic AI Foundation as a Growth Stage project alongside MCP, goose, and AGENTS.md, with more than 150 backing organizations. IBM’s rival Agent Communication Protocol merged into A2A in August 2025, consolidating the agent-to-agent space.

Status
#

Active, spec-stable, unevenly adopted. v1.0.0 shipped 2026-03-12 and v1.0.1 on 2026-05-28 (latest as of 2026-09-13), with breaking wire changes from 0.3 but backward-compatible Agent Cards. The repository shows about 25.7k stars as of 2026-09-13, and the launch coalition of 50+ partners passed 100 supporting companies by donation time. Support concentrates in enterprise suites (Gemini Enterprise, Agentforce, watsonx Orchestrate, SAP Joule, Azure AI Foundry). No coding harness in this index speaks it natively; the closest touchpoint is Gemini CLI, where community setups attach remote A2A agents.

Strengths
#

  • Solves discovery, delegation, and long-running tasks across trust boundaries, which plain REST leaves to every integrator.
  • Web-aligned core: an interaction can begin with a single HTTP request and scale through existing load balancers, gateways, and observability.
  • Six official SDKs (Python, Go, JavaScript, Java, .NET, Rust) under genuinely neutral governance.
  • Signed Agent Cards give cryptographic identity verification before any interaction.

Cautions
#

  • The usage gap with MCP is the signal: an A2A ecosystem developer reported roughly 10.9M monthly a2a-sdk downloads versus about 257M for the MCP SDK (pypistats, mid-June 2026).
  • Critics argue MCP already covers the ground by treating agents as tools, and a June 2026 Ask HN thread (45 comments) found thin startup usage plus concrete complaints about identity assumptions and gRPC friction.
  • v1.0 broke wire compatibility with v0.3, so early adopters are mid-migration.
  • Prompt injection across agent boundaries remains unsolved at the protocol level.

Pricing
#

Free and open, Apache-2.0, with nothing to buy. Google monetizes the surrounding platforms (Gemini Enterprise, ADK), not the protocol.

Compared to
#

  • MCP: agent-to-tool, complementary by design; the official framing is MCP inside agents, A2A between agents.
  • ACP: editor-to-agent for coding agents, local-first; A2A is organization-to-organization and remote-first.
  • REST plus an OpenAPI spec: adequate for one-to-one integrations, with no discovery or task lifecycle.

Bottom line
#

Recommended when agents from different vendors or departments must delegate work across a boundary; not for wiring up your own sub-agents, where native primitives or MCP are simpler. The disagreeable part: I expect A2A to stay an enterprise convention, and if autonomous agents on the open web ever emerge they will speak MCP or plain HTTP first, not A2A.

Changes
#

  • 2026-08-24 - Created in the Protocols category seed.
  • 2026-09-05 - Corrected the v1.0.1 release date to 2026-05-28 per the GitHub API.

See also
#

References
#