A2A Agent Delegation
CrewAI supports the Agent-to-Agent (A2A) protocol, allowing agents to delegate tasks to remote specialized agents. The agent’s LLM automatically decides whether to handle a task directly or delegate to an A2A agent based on the task requirements.A2A delegation requires the
a2a-sdk package. Install with: uv add 'crewai[a2a]' or pip install 'crewai[a2a]'How It Works
When an agent is configured with A2A capabilities:- The LLM analyzes each task
- It decides to either:
- Handle the task directly using its own capabilities
- Delegate to a remote A2A agent for specialized handling
- If delegating, the agent communicates with the remote A2A agent through the protocol
- Results are returned to the CrewAI workflow
Basic Configuration
Configure an agent for A2A delegation by setting thea2a parameter:
Code
Configuration Options
TheA2AConfig class accepts the following parameters:
The A2A agent endpoint URL (typically points to
.well-known/agent-card.json)Authentication scheme for the A2A agent. Supports Bearer tokens, OAuth2, API keys, and HTTP authentication.
Request timeout in seconds
Maximum number of conversation turns with the A2A agent
Optional Pydantic model for requesting structured output from an A2A agent. A2A protocol does not
enforce this, so an A2A agent does not need to honor this request.
Whether to raise an error immediately if agent connection fails. When
False, the agent continues with available agents and informs the LLM about unavailable ones.Authentication
For A2A agents that require authentication, use one of the provided auth schemes:- Bearer Token
- API Key
- OAuth2
- HTTP Basic
Code
Multiple A2A Agents
Configure multiple A2A agents for delegation by passing a list:Code
Error Handling
Control how agent connection failures are handled using thefail_fast parameter:
Code
fail_fast=False:
- If some agents fail, the LLM is informed which agents are unavailable and can delegate to working agents
- If all agents fail, the LLM receives a notice about unavailable agents and handles the task directly
- Connection errors are captured and included in the context for better decision-making
Best Practices
Set Appropriate Timeouts
Configure timeouts based on expected A2A agent response times. Longer-running tasks may need higher timeout values.
Limit Conversation Turns
Use
max_turns to prevent excessive back-and-forth. The agent will automatically conclude conversations before hitting the limit.Use Resilient Error Handling
Set
fail_fast=False for production environments with multiple agents to gracefully handle connection failures and maintain workflow continuity.Secure Your Credentials
Store authentication tokens and credentials as environment variables, not in code.
Monitor Delegation Decisions
Use verbose mode to observe when the LLM chooses to delegate versus handle tasks directly.
Supported Authentication Methods
- Bearer Token - Simple token-based authentication
- OAuth2 Client Credentials - OAuth2 flow for machine-to-machine communication
- OAuth2 Authorization Code - OAuth2 flow requiring user authorization
- API Key - Key-based authentication (header, query param, or cookie)
- HTTP Basic - Username/password authentication
- HTTP Digest - Digest authentication (requires
httpx-authpackage)
