Technology · Agentic → Agent Protocols · Open Source · wiki:deep
Agent2Agent (A2A) is an open protocol for communication and interoperability between opaque agentic applications — agents built on different frameworks, by different vendors, on separate servers — so they can collaborate as peers, not merely as tools. Agents discover capabilities via Agent Cards, negotiate modalities (text, forms, media), and collaborate on long-running tasks without exposing internal state, memory, or tools. Wire format: JSON-RPC 2.0 over HTTP(S), with sync, SSE streaming, and async push. Linux Foundation project (Google-contributed); Apache-2.0; SDKs in Python, Go, JS, Java, .NET, Rust.
An agentic OS that only mounts tools still needs a peer handoff language when work crosses products or companies. A2A is the research pick for agent↔agent discovery and task exchange. Prefer MCP for host↔tool/resources/prompts; use both when specialists are external agents and tools are MCP servers. Protocol alone does not replace policy gates or the ledger.
Publish an Agent Card; peers discover and open authenticated sessions; clients send tasks/messages and receive artifacts via request/response, streaming, or push. Opacity: collaborate without sharing proprietary internals.
Related: model-context-protocol · topics/33-skill-registry
Scroll inside the canvas to pan
Catalog backlinks — what points here (wiki “what links here”).
Claims below are backed by science sources on disk.
Protocol / interoperability role
a2aproject/A2A repository · MODERATE
“An open protocol enabling communication and interoperability between opaque agentic applications.”
Spec notes
Agent2Agent (A2A) Protocol Specification · MODERATE
“The Agent2Agent (A2A) Protocol is an open standard designed to facilitate communication and interoperability between independent, potentially opaque AI agent systems.”
MCP vs A2A contrast
MCP vs A2A — coordination complexity · MODERATE
“A task represents a stateful and long-running piece of work whose progress needs to be tracked by the client and the server.”
Features and peers linked from the catalog map — not a second product surface.
No DM vendor crosswalk edges yet.
Primary repo github.com/a2aproject/A2A · Open Source
technologies/agent2agent-protocol/README.md
9 tags · 6 out · 7 in · 3 artifacts · 1 gaps · 26 corpus docs
map_edge · 5
tech_features · 1
tech_quote · 6
tech_readme · 1
tech_science_source · 3
tech_section · 10