A2A Protocol v1.2 — The Standard for AI Agent-to-Agent Communication

Posted on: 4/26/2026 6:14:13 PM

In today's increasingly complex AI landscape, organizations don't just have one AI agent — they have dozens, sometimes hundreds, of specialized agents. The question arises: how can agents from different frameworks, different vendors discover each other, communicate, and collaborate without custom integration for every pair? That's exactly the problem A2A Protocol (Agent-to-Agent) was built to solve.

1. Why Do We Need A2A Protocol?

Imagine an enterprise system with:

• HR Agent (built on LangGraph) handling recruitment
• Finance Agent (built on Semantic Kernel) managing budgets
• IT Support Agent (built on CrewAI) providing technical assistance

When a new employee is hired, the HR Agent needs to request the Finance Agent to allocate equipment budget, while simultaneously asking the IT Support Agent to create an email account. Without a common protocol, you'd need N × M custom integrations for every agent pair — a maintenance nightmare.

graph LR
    A[HR Agent
LangGraph] -->|A2A| B[Finance Agent
Semantic Kernel]
    A -->|A2A| C[IT Support Agent
CrewAI]
    B -->|A2A| D[Procurement Agent
AutoGen]
    C -->|A2A| D
    style A fill:#e94560,stroke:#fff,color:#fff
    style B fill:#2c3e50,stroke:#fff,color:#fff
    style C fill:#2c3e50,stroke:#fff,color:#fff
    style D fill:#16213e,stroke:#fff,color:#fff

2. Evolution Timeline

3. Core Architecture

A2A is designed around 5 central concepts:

3.1 Agent Card — The Agent's Digital Identity

An Agent Card is a JSON metadata document published by an A2A Server, describing its identity, capabilities, skills, service endpoint, and authentication requirements. It's the discovery mechanism — allowing other agents to know who you are and what you can do.

{
  "name": "Finance Agent",
  "description": "Budget management, expense approval, financial reporting",
  "url": "https://agents.company.com/finance",
  "version": "1.2",
  "skills": [
    {
      "id": "budget-approval",
      "name": "Budget Approval",
      "description": "Approve spending requests under $10,000"
    },
    {
      "id": "expense-report",
      "name": "Expense Report",
      "description": "Generate expense reports by department"
    }
  ],
  "securitySchemes": {
    "oauth2": {
      "type": "oauth2",
      "flows": {
        "clientCredentials": {
          "tokenUrl": "https://auth.company.com/token",
          "scopes": { "finance:read": "", "finance:write": "" }
        }
      }
    }
  }
}

3.2 Task — The Unit of Work

Each request between agents creates a Task — a stateful unit of work with interaction history and outputs. Tasks maintain state throughout their lifecycle, enabling asynchronous processing.

stateDiagram-v2
    [*] --> Submitted
    Submitted --> Working : Agent starts processing
    Working --> Completed : Success
    Working --> Failed : Error
    Working --> Canceled : Client cancels
    Working --> InputRequired : Needs more info
    Working --> AuthRequired : Needs authentication
    Submitted --> Rejected : Agent refuses
    InputRequired --> Working : Client provides info
    AuthRequired --> Working : Client authenticates
    Completed --> [*]
    Failed --> [*]
    Canceled --> [*]
    Rejected --> [*]

Notable are the InputRequired and AuthRequired states — these are interrupted states enabling multi-turn interaction. An agent can request additional information or authentication before proceeding, similar to how humans ask clarifying questions.

3.3 Message, Artifact, and Part

4. Transport Bindings — Three Ways to Communicate

A2A v1.2 supports 3 transport bindings for different use cases:

Example: Sending a Message via HTTP/REST

POST /messages HTTP/1.1
Host: agents.company.com
Content-Type: application/json
A2A-Version: 1.2
Authorization: Bearer eyJhbGciOiJSUzI1NiIs...

{
  "message": {
    "role": "user",
    "parts": [
      {
        "text": "Generate Q1/2026 expense report for Engineering department"
      }
    ]
  },
  "configuration": {
    "acceptedOutputModes": ["text", "file"],
    "blocking": false
  }
}

Example: Streaming Response via SSE

POST /messages:stream HTTP/1.1
Host: agents.company.com
A2A-Version: 1.2

---
event: TaskStatusUpdateEvent
data: {"taskId":"t-123","status":{"state":"working","message":"Querying data..."}}

event: TaskArtifactUpdateEvent
data: {"taskId":"t-123","artifact":{"parts":[{"text":"Total Q1 spending: $234,500"}]}}

event: TaskStatusUpdateEvent
data: {"taskId":"t-123","status":{"state":"completed"}}

5. Async Result Delivery Mechanisms

Not every task completes instantly. A2A provides 3 mechanisms for tracking long-running tasks:

graph TB
    subgraph Polling
        A1[Client] -->|GET /tasks/id| B1[Server]
        B1 -->|Task status| A1
    end
    subgraph Streaming
        A2[Client] -->|GET /tasks/id:subscribe| B2[Server]
        B2 -->|SSE events| A2
    end
    subgraph Push Notification
        A3[Client] -->|Register webhook| B3[Server]
        B3 -->|HTTP POST events| C3[Client Webhook]
    end
    style A1 fill:#f8f9fa,stroke:#e94560,color:#2c3e50
    style A2 fill:#f8f9fa,stroke:#e94560,color:#2c3e50
    style A3 fill:#f8f9fa,stroke:#e94560,color:#2c3e50
    style B1 fill:#e94560,stroke:#fff,color:#fff
    style B2 fill:#e94560,stroke:#fff,color:#fff
    style B3 fill:#e94560,stroke:#fff,color:#fff
    style C3 fill:#2c3e50,stroke:#fff,color:#fff

6. Security — Beyond Just OAuth

The A2A specification mandates rigorous multi-layer security:

• Transport Security: HTTPS required for all communication
• Authentication: Supports API Key, HTTP Bearer, OAuth 2.0, OpenID Connect, Mutual TLS
• Signed Agent Cards (v1.2): Cryptographic signatures verify agent identity, preventing impersonation
• Capability-based Authorization: Servers only grant access to authorized resources
• Information Leakage Prevention: Servers MUST NOT distinguish between "not found" and "not authorized" — preventing enumeration attacks

// OAuth 2.0 Client Credentials flow for agent-to-agent
{
  "securitySchemes": {
    "agent_oauth": {
      "type": "oauth2",
      "flows": {
        "clientCredentials": {
          "tokenUrl": "https://auth.company.com/oauth2/token",
          "scopes": {
            "agent:execute": "Execute tasks",
            "agent:read": "Read task results"
          }
        }
      }
    }
  }
}

7. A2A vs MCP — Complementary, Not Competing

The most common question: "Should I use A2A or MCP?" The answer: both.

graph TB
    U[User] --> O[Orchestrator Agent]
    O -->|A2A| AG1[Analysis Agent]
    O -->|A2A| AG2[Report Writer Agent]
    O -->|A2A| AG3[Email Agent]
    AG1 -->|MCP| T1[Database Tool]
    AG1 -->|MCP| T2[Analytics API]
    AG2 -->|MCP| T3[Template Engine]
    AG3 -->|MCP| T4[Email Service]
    style U fill:#f8f9fa,stroke:#e94560,color:#2c3e50
    style O fill:#e94560,stroke:#fff,color:#fff
    style AG1 fill:#2c3e50,stroke:#fff,color:#fff
    style AG2 fill:#2c3e50,stroke:#fff,color:#fff
    style AG3 fill:#2c3e50,stroke:#fff,color:#fff
    style T1 fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50
    style T2 fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50
    style T3 fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50
    style T4 fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50

8. Multi-Turn Interaction

A powerful A2A feature is multi-turn interaction via contextId. This enables:

• Agents asking for clarification when information is missing (InputRequired state)
• Related tasks grouped within the same conversational context
• Agents maintaining conversational history across interactions

// Turn 1: Client sends request
{
  "message": {
    "role": "user",
    "parts": [{ "text": "Approve spending for the Backend team" }]
  }
}

// Server responds: needs more info
{
  "taskId": "t-456",
  "contextId": "ctx-789",
  "status": { "state": "input-required", "message": "What is the specific amount?" }
}

// Turn 2: Client provides info (same contextId)
{
  "message": {
    "role": "user",
    "contextId": "ctx-789",
    "taskId": "t-456",
    "parts": [{ "text": "$8,500 for Q2 software licenses" }]
  }
}

9. Ecosystem and SDKs

A2A has been natively integrated into the most popular agent frameworks:

Quick Start with Google ADK

# Create project with A2A support
uvx agent-starter-pack create my-finance-agent -a adk@gemini-fullstack

# Agent Card auto-generated at /.well-known/agent.json
# Deploy to Cloud Run
gcloud run deploy my-finance-agent --source .

10. Production Deployments — Who's Using It?

A2A isn't just a paper specification — major organizations have deployed it in production:

• Tyson Foods & Gordon Food Service: Supply chain systems with multiple A2A agents sharing product data and sales leads in real-time
• Adobe: Creative content agents coordinating via A2A
• ServiceNow: IT workflow agents auto-routing tickets through A2A
• S&P Global: Financial analysis agents communicating cross-domain
• Salesforce, SAP, Twilio: A2A integrated into their platform agent ecosystems

11. Real-World System Design with A2A

Here's a reference architecture for an order management system using A2A:

graph TB
    GW[API Gateway] --> OA[Order Agent]
    OA -->|A2A: check inventory| IA[Inventory Agent]
    OA -->|A2A: process payment| PA[Payment Agent]
    OA -->|A2A: create shipment| SA[Shipping Agent]
    PA -->|A2A: fraud check| FA[Fraud Detection Agent]
    SA -->|A2A: send notification| NA[Notification Agent]
    IA -->|MCP| DB1[(Inventory DB)]
    PA -->|MCP| PS[Payment Service]
    SA -->|MCP| LP[Logistics Partner API]
    NA -->|MCP| ES[Email/SMS Service]
    style GW fill:#f8f9fa,stroke:#e94560,color:#2c3e50
    style OA fill:#e94560,stroke:#fff,color:#fff
    style IA fill:#2c3e50,stroke:#fff,color:#fff
    style PA fill:#2c3e50,stroke:#fff,color:#fff
    style SA fill:#2c3e50,stroke:#fff,color:#fff
    style FA fill:#16213e,stroke:#fff,color:#fff
    style NA fill:#16213e,stroke:#fff,color:#fff
    style DB1 fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50
    style PS fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50
    style LP fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50
    style ES fill:#f8f9fa,stroke:#2c3e50,color:#2c3e50

12. Best Practices for A2A Deployment

Conclusion

A2A Protocol v1.2 marks the maturation of agent-to-agent communication: from a Google proposal to an open standard under the Linux Foundation with 150+ participating organizations. Combined with MCP for agent-to-tool connections, the A2A + MCP duo creates a complete communication foundation for multi-agent AI ecosystems.

With signed Agent Cards, multi-turn interaction, and 3 flexible transport bindings, A2A is production-ready. If you're operating more than one AI agent — it's time to seriously consider A2A.

References

• A2A Protocol Specification v1.2
• Google Developers Blog — Announcing A2A Protocol
• Google Cloud Blog — A2A Protocol Upgrades
• A2A Protocol GitHub Repository
• Developer's Guide to AI Agent Protocols — Google