Multi-agent
What is A2A?
Also known as: agent-to-agent
Agent-to-agent (A2A) protocols define how separate agent hosts exchange tasks and artifacts.
Inter-agent protocols still need typed payloads and human-visible stop rules.
Why it matters
Agent-to-agent (A2A) protocols define how separate agent hosts exchange tasks and artifacts. As agent systems grow, they need standardized ways to communicate — just as microservices need APIs.
A2A protocols must handle typed payloads, authentication, and human-visible stop rules. Without them, inter-agent communication is fragile and opaque.
Key takeaways
- 1A2A protocols standardize inter-agent communication.
- 2They need typed payloads and visible stop rules.
- 3A2A is for communication between separate agent systems, not agents within one system.
Common mistakes
- ✕Using A2A protocols for intra-system communication when function calls suffice.
- ✕Not defining error handling for failed inter-agent calls.
Related terms
Concept neighborhood
Terms linked from A2A in the glossary graph.