Skip to content
sync ai agents

What is A2A?

Updated November 2026

A2A, short for Agent2Agent, is an open protocol for communication between independently implemented agent applications. It lets one agent request work from another without requiring access to the other agent’s internal tools, memory, or decision logic.

What does A2A standardize?

The official A2A documentation describes interoperability across agent frameworks and vendors. The important boundary is the external service contract: a caller interacts with an agent’s advertised capabilities rather than importing its implementation. This supports delegation across organizational or deployment boundaries without pretending every participant shares one runtime.

In practice, an integration needs capability discovery, request and response handling, and a way to track work that does not finish immediately. Treat capability descriptions as routing inputs, not proof that an agent can safely complete every matching request.

How does A2A differ from MCP?

The official documentation presents A2A and MCP as complementary. A2A connects agent applications; MCP connects AI applications to external tools and data. An agent receiving an A2A request can use MCP internally, but neither protocol chooses the business workflow.

BoundaryTypical interaction
A2ADelegate a research task to another agent
MCPRead records or invoke an exposed tool
Application policyAuthorize access and approve consequences

What can fail across an agent boundary?

A remote agent might accept work and then become unavailable, or return an answer whose assumptions differ from the caller’s. Set deadlines, preserve request identifiers, and define how cancellation and retries interact with side effects. A transport response alone is not evidence that the business outcome succeeded.

Interoperability reduces custom integration work but adds distributed failure modes. Validate returned artifacts and access permissions at the receiving boundary, and record enough execution history to investigate conflicting results without exposing unnecessary private context.

What else should you know?

  • Does A2A replace MCP?

    No. They address different boundaries and can be used together.

  • Does A2A require shared memory?

    No. Agents can communicate while keeping their internal state private.

  • Does compatibility establish trust?

    No. Authentication, authorization, and output validation remain necessary.

  • When is A2A unnecessary?

    A local function call may suffice when components share one application boundary.

Where can you go deeper?