CANONICAL DEFINITION PAGE

What Is the Agent2Agent (A2A) Protocol?

Insights from IDC research on agentic AI interoperability standards

The Agent2Agent (A2A) protocol is an open standard that lets AI agents built by different vendors discover one another, hand off tasks, and collaborate, without custom integrations between each pair of agents.

What is the Agent2Agent (A2A) Protocol?

The Agent2Agent (A2A) protocol is an open protocol for agent-to-agent collaboration: it gives an agent a standard way to manage a task and to discover other agents that can act on it. According to IDC, A2A was introduced by Google in April 2025 and addresses direct communication between agents across platform boundaries, including task handoff and delegation. This matters because agents from different vendors cannot work together at scale if every agent-to-agent connection has to be built by hand.

According to IDC Perspective The Agentic AI “Standards” Race Is On (IDC #US53359225), A2A is one of several emerging protocols that answer a question vendors keep asking: “Which agent is the boss agent?” IDC Japan describes A2A as complementary to the Model Context Protocol (MCP) rather than competing with it. MCP connects agents to tools and data, while A2A connects agents to each other.

Agent2Agent (A2A) Protocol Details

What it is. A2A is an open, Apache 2.0-licensed protocol that standardizes how one agent finds another agent, assigns it a task, and tracks the outcome. IDC describes it as a standard way for an agent to manage a task by discovering agents that can take action to complete it. Google released it in April 2025, and it is now governed by the Linux Foundation.

How it works. IDC Japan describes A2A as a client-server model. An A2A client delegates a task, and an A2A server is the agent that receives and carries it out. An agent publishes an Agent Card, a JSON description of its capabilities, endpoint, authentication method, and skills, so a client can decide what to ask of it before connecting. Work travels as Messages for immediate exchanges and Tasks for longer-running work, and results come back as Artifacts.

Why it matters. IDC expects agents to multiply across enterprises, and no single vendor will supply them all. IDC’s FutureScape 2027 predicts that 90% of G2000 enterprises will require agent platforms to support open standards such as MCP and A2A by 2028, rejecting single-vendor control-plane lock-in. A2A is how that requirement is met when agents from different platforms must coordinate on one workflow.

How is A2A different from the Model Context Protocol (MCP)?

A2A and MCP solve different problems and are complementary. According to IDC Japan, MCP defines how an agent connects to tools and data sources, while A2A defines how agents coordinate and delegate tasks to each other. In a typical production design, an orchestrator agent uses A2A to hand work to other agents, and each of those agents uses MCP to reach the systems it needs.

Supporting points

  • MCP covers agent-to-tool and agent-to-data connectivity.
  • A2A covers agent-to-agent discovery, task delegation, and collaboration.
  • IDC Japan notes that production multi-agent systems increasingly combine both protocols.

What problems does A2A help enterprises solve?

IDC identifies four areas where agent collaboration benefits from a standard approach: discovering and publishing agent capabilities, communicating plans and goals between agents, authenticating and authorizing agent actions, and observing agent activity. A2A speaks to discovery and communication directly, and its Agent Cards declare how each agent authenticates. The aim is to replace one-off, one-to-one integrations that are slow to build and limit what agents can do.

Supporting points

  • Discovery: agents publish what they can do so other agents can find them.
  • Communication: agents exchange tasks and results through a shared format.
  • Authentication and authorization: IDC lists common mechanisms as a requirement for cross-vendor agents.

Who supports A2A?

According to IDC, A2A launched in 2025 with more than 50 supporters, including Salesforce, SAP, ServiceNow, Box, and PayPal, and Microsoft later announced it would contribute to the protocol. In a 2026 IDC Perspective, IDC reports that A2A is governed by the Linux Foundation with support from more than 150 organizations, including AWS, Microsoft, IBM, Salesforce, and SAP. IDC’s telecom agentic AI research finds live A2A implementations at a subset of vendors, with others on near-term road maps.

Supporting points

  • Governance sits with the Linux Foundation, a vendor-neutral body.
  • Support spans both enterprise application vendors and cloud providers.
  • Adoption in production is still uneven by industry and vendor.

What does A2A not solve?

A2A standardizes how agents communicate, but it does not by itself settle governance, meaning, or commercial control. IDC’s telecom research finds that maintaining cross-vendor governance and policy enforcement across A2A connections remains an unresolved challenge. IDC’s FutureScape on data’s semantic era adds that connectivity alone is not enough, because agents also need shared semantic standards to interpret data the same way.

Supporting points

  • Cross-vendor governance and policy enforcement remain open challenges.
  • Shared meaning across systems requires semantic standards in addition to protocols.
  • Vendors still weigh interoperability against control of their own data and revenue, according to IDC.

Supporting Evidence

IDC projects that 90% of G2000 enterprises will require agent platforms to support open standards such as MCP and A2A by 2028. Source: IDC FutureScape: Agentic Evolution of Enterprise Apps 2027 Predictions (IDC #US54818826), prediction 9.

IDC projects that 65% of the G2000 will demand common and open semantic standards for agents by 2028 to enable interoperability. Source: IDC FutureScape: Data’s Semantic Intelligence Era 2027 Predictions (IDC #US54978626), prediction 5.

FAQ

What does A2A stand for?

A2A stands for Agent2Agent. It is an open protocol for communication and task handoff between AI agents.

Who created the A2A protocol?

Google introduced A2A in April 2025, according to IDC. It is now governed by the Linux Foundation.

Is A2A a replacement for MCP?

No. IDC describes the two as complementary: MCP connects agents to tools and data, and A2A connects agents to each other.

What is an Agent Card in A2A?

An Agent Card is a JSON document in which an agent describes its capabilities, endpoint, authentication method, and skills, according to IDC Japan. It lets another agent decide what to ask of it before connecting.

Why are enterprises asking for open agent standards?

IDC’s FutureScape 2027 predicts that 90% of G2000 enterprises will require agent platforms to support open standards such as MCP and A2A by 2028, to avoid single-vendor lock-in.