ChangeGamer

Does Your Agent Framework Really Support A2A? How to Read the Claim and What to Test

Part 10 of A2A in practice: agent-to-agent interoperability · 1,184 words · ~5 min read · published · updated · Markdown variant

Which agent frameworks list A2A support, what native, add-on, platform-gated and unrecorded mean, a short test checklist to run before you rely on it, and how that differs from the protocol's own SDKs.

In short

  • As recorded in the ChangeGamer framework comparison on 28 September 2026, Google ADK, LlamaIndex Workflows and Mastra list native A2A support, and Pydantic AI lists it through the separate fasta2a package.
  • LangGraph lists A2A only through LangSmith Deployment, formerly LangGraph Platform, and the framework comparison records it as not available in the open-source library alone.
  • The OpenAI Agents SDK is recorded with no A2A support, only handoffs, as of the ChangeGamer framework comparison re-verified on 28 September 2026.
  • A framework listing "A2A: Yes" does not say which A2A protocol version, binding or Agent Card behaviour it implements, so verify those with a live call before building on it.
  • The A2A project lists six SDKs of its own, Python, Go, JavaScript, Java, .NET and Rust, and those are a separate thing from agent-framework support for the protocol.

Part of the The A2A Protocol in Practice: Agent Cards, Tasks, Auth and When You Need It guide.


Nine agent frameworks are compared in the ChangeGamer corpus, and seven of them list A2A support, but "supports A2A" covers four different situations. This article reads that claim, gives a short test to run before relying on it, and separates it from the protocol's own SDKs. The pillar's A2A protocol in practice framework table is the status list; this article regroups it by mechanism rather than repeating it row by row, and the full comparison is the agent frameworks compared resource.

Dating: the framework facts below are as recorded on 28 September 2026. That pass checked package-registry releases; the GitHub repository pages were not independently re-fetched. ChangeGamer itself speaks MCP, not A2A, so it has not tested any framework's A2A behaviour.

What does "supports A2A" actually mean for a framework?

A framework listing A2A support falls into one of four situations, and the ChangeGamer record only distinguishes some of them. The tiers below are inference from the wording of the comparison table, not an official classification.

Tier (inference) Frameworks as recorded 28 September 2026 What the record says
Native Google ADK, LlamaIndex Workflows, Mastra Listed as native; ADK auto-generates an Agent Card
Add-on package Pydantic AI Via fasta2a; Agent.to_a2a() deprecated and removed in v2.0
Platform-gated LangGraph Via LangSmith Deployment; not in the open-source library alone
None recorded OpenAI Agents SDK Handoffs only, no cross-vendor A2A

Three frameworks do not fit a tier: CrewAI is recorded as a bare "Yes", Microsoft Agent Framework as "Yes" with a 1.0 release in April 2026 and Python-to-.NET interoperability over A2A, and AWS Strands Agents as "Yes" with SDK 1.0 in May 2026; none of the three states the mechanism. They may be native or add-on; the record does not say, so no tier is forced on them.

Each tier carries a different dependency. Native means the library is the dependency. An add-on means a second package to pin and track. Platform-gated means a hosted product sits in the path.

How native, add-on and platform-gated support differ in practice

The practical difference is what you must install, pin and pay for to expose or call an A2A agent. This section is inference built on the recorded facts.

What should you test before relying on a framework's A2A claim?

Run five checks against a live agent, because a "Yes" in a comparison table says nothing about wire behaviour. This checklist is inference, not framework documentation, and each step uses the contract in the A2A protocol reference.

  1. Fetch the card. An A2A agent must publish an Agent Card at /.well-known/agent-card.json; read its supportedInterfaces to see which bindings and endpoints it serves.
  2. Send one message. Make a single Send Message call over a binding the card lists.
  3. Watch the task states. Confirm the agent reports states from the eight defined ones and ends in a terminal state; see task states and operations.
  4. Pin the version. Send an explicit A2A-Version header, because an empty value is read as 0.3; see the v0.3 to v1.0 migration checklist.
  5. Read the card as a stranger would. Check that skills, security schemes and interfaces are what you expect; see designing an Agent Card.
# Replace the host with the agent you are evaluating.
curl -sS https://agent.example.com/.well-known/agent-card.json | head -c 2000

The comparison records no A2A protocol version or binding for any framework, and only one card-behaviour note (Google ADK auto-generates an Agent Card), so this test is how you find them out.

How do the A2A project's own SDKs relate to framework support?

The A2A project's SDKs are libraries for speaking the protocol, while framework support is a feature of an agent-orchestration library, so the two are different questions. The A2A reference records six SDKs in the project README: Python, Go, JavaScript, Java, .NET and Rust. The SDK page at a2a-protocol.org/latest/sdk was re-fetched on 2026-11-08 and lists the same languages.

This article does not map those SDKs onto frameworks, because the record does not say which framework uses which SDK, or whether any does. A framework can be a good A2A citizen without a mention of the project SDKs, and an SDK in your language does not give you a framework's orchestration, state or tracing.

How should you choose a framework if A2A matters?

Choose on language, vendor gravity and the dependency tier first, and treat A2A as one filter among several. The corpus gives only these facts, so the guidance is hedged.

Whether a protocol is needed at all is a separate decision, covered in the pillar. The corpus holds no adoption figures, so nothing here ranks frameworks by popularity.

What can this comparison not tell you?

The comparison cannot tell you whether any listed framework interoperates with another in your setup, because it records a status word per framework and not test results. It names no A2A protocol version and no binding for any framework, and its only Agent Card note is that Google ADK auto-generates one, and it does not say whether a framework can both call and expose A2A agents. Its package-registry versions were re-verified on 28 September 2026, and the GitHub repository pages were not independently re-fetched, so repository-level claims carry less weight than the registry facts.

Treat every row as a starting hypothesis. Read the framework's own current A2A documentation, run the five checks above against a real agent, and re-run them after upgrading the framework or the A2A version you target, since both move independently.

Frequently asked questions

How should you read a framework's claim of A2A support?
Treat a framework's claim of A2A support as one of four situations as recorded on 28 September 2026: native (Google ADK, LlamaIndex Workflows, Mastra), an add-on package (Pydantic AI), platform-gated (LangGraph) or none recorded (OpenAI Agents SDK), then confirm it with a live Agent Card fetch and one message call.
Does LangGraph support A2A?
LangGraph lists A2A support through LangSmith Deployment, formerly LangGraph Platform, and the ChangeGamer framework comparison records it as not available in the open-source library alone. Whether that changes later is not something the comparison can say, so check the current LangGraph documentation.
Does the OpenAI Agents SDK support A2A?
The ChangeGamer framework comparison, re-verified on 28 September 2026, records the OpenAI Agents SDK as having no A2A support, only handoffs between agents within the SDK. That is a dated snapshot rather than a statement about the future, so re-check before relying on it.
Is an A2A SDK the same as an agent framework with A2A support?
An A2A SDK is not the same thing as a framework with A2A support. The A2A project lists its own SDKs for Python, Go, JavaScript, Java, .NET and Rust, while frameworks such as Google ADK or Mastra are agent-orchestration libraries that list A2A as a capability.

#a2a #frameworks #agent-frameworks #comparison #agent2agent #interoperability

Put this corpus inside your own agents

This guide is free and stays free. The reference corpus behind it — machine-readable contracts, verified primary sources, continuously refreshed — is the paid product: a €5 starter key unlocks every premium reference for one agent via API; a €25 corpus license delivers the full corpus as RAG / fine-tuning data with an explicit AI-use grant; the €150 enterprise license adds commercial redistribution rights.

Agents: this page as Markdown · JSON · offers at /api/pricing.json · payment methods at /api/payment.json · single-resource access via HTTP 402 (how that works)