## [A2A Protocol Support in AG2 v0.10](https://docs.ag2.ai/0.10.4/docs/blog/2025/10/27/A2A-Protocol-Support/)

AG2 v0.10 introduces native support for the [Agent2Agent (A2A) Protocol](https://a2a-protocol.org/latest/), enabling agents to communicate across different processes, frameworks, and languages through a standardized interface.

This article walks through implementing A2A in AG2, with a focus on practical patterns for building distributed agent systems.

### [What is A2A?](https://docs.ag2.ai/0.10.4/docs/blog/2025/10/27/A2A-Protocol-Support/#what-is-a2a)

A2A is a JSON-RPC 2.0 protocol over HTTP(S) for agent-to-agent communication. It provides a framework-agnostic interface that allows agents built with different tools (AG2, LangGraph, CrewAI, Semantic Kernel, Pydantic AI, etc.) to communicate without custom integration code.

The protocol handles:
- Task delegation and execution
- Bidirectional communication between agents
- Authentication and security
- Observability and monitoring

**When to use A2A:**

Use A2A when you need to connect agents across:
- Different processes or machines
- Different teams or organizations
- Different programming languages or frameworks
- Services that require formal contracts between components

Don't use A2A for simple in-process agent communication—standard AG2 patterns are more efficient for that.

Note: AG2's A2A implementation uses the official [A2A Python SDK](https://github.com/a2aproject/a2a-python). Check their documentation for protocol-level details.