Standard · Converse
A2A (Agent2Agent) and agent cards
How one agent hands a task or a message to another, with a card describing each.
Emerging
What it is
A2A lets agents from different makers send each other tasks and messages. Each publishes an agent card that lists its skills and the interfaces it speaks.
An analogy
A business card and a switchboard for agents: who I am, what I do and how to reach me.
At a glance
- Owner
- Created by Google; given to the Linux Foundation in June 2025
- Maturity
- Emerging Version 1.0 reported in March 2026. In 1.0 an agent card, published at /.well-known/agent-card.json, can be signed (JWS).
- Where it lives
- a2a-protocol.org
- Framework domain
- Converse: Be asked
- What it serves
- Let other agents hand work to yours
- Describe what your agent can do
Who should care
The roles this standard touches most. See all the roles on the personas page.
- Engineering and product. Build the access, data, endpoints and actions that agents use, on open standards.
- Service and operations. Answer agents’ questions, hand off to people well and keep promises made through agents.
How to adopt it
- 1
Publish an agent card only if you run an agent that other agents should call.
- 2
List its skills in plain words.
- 3
Sign the card and use the current version.
The Institute’s view
Adopt with care
Valuable once you run an agent that others should reach. Most organizations are better served by MCP first. Do not publish a card for an agent you do not operate.
Standards change fast. Last reviewed November 2026.