#a2a
4 resources and 13 guides tagged #a2a on ChangeGamer. Includes MCP vs A2A: Two Protocols, Two Roles and AI Agent Frameworks Compared.
- MCP vs A2A: Two Protocols, Two Roles Compact comparison of the Model Context Protocol (agent↔tool) and the Agent2Agent Protocol (agent↔agent): purpose, topology, transport, discovery, auth, governance, and when to use each.
- AI Agent Frameworks Compared Vendor-neutral comparison table of the major agent-orchestration frameworks — language, license, multi-agent model, MCP/A2A support — plus a how-to-choose guide for agent builders.
- A2UI: Google's Declarative Agent-to-UI Protocol (vs AG-UI, MCP Apps) What A2UI is: the open, Apache-2.0 standard in which agents send declarative JSON describing the intent of a UI and the client renders it from a catalog it controls; the four v0.9 message types, transport requirements, renderer status, and how A2UI relates to AG-UI, A2A and MCP Apps.
- A2A Protocol (Agent2Agent): Agent Card, Operations, Task States, Bindings Wire-level reference for the A2A (Agent2Agent) protocol v1.0: the Agent Card at /.well-known/agent-card.json, the 11 operations, the 8 task states, three protocol bindings, security schemes, version negotiation, and what changed from v0.3.
Guides
- The A2A Protocol in Practice: Agent Cards, Tasks, Auth and When You Need It A practical guide to the A2A (Agent2Agent) protocol: what it standardizes, when it beats in-process subagents, how Agent Cards, task states, bindings and authentication work, how credentials cross agent hops, and how to launch it.
- Do You Need A2A for a Multi-Agent System? A Decision Rule A decision rule for choosing between in-process subagents and the A2A protocol: start with one agent, add more only for a named failure, and cross the network with A2A only when a remote party, framework or trust boundary demands it.
- Designing an Agent Card: What Goes in the Public Card and What Waits How to design an A2A Agent Card: the field groups, the well-known path, optional signing, and a rule for splitting what the public card advertises from what an authenticated client fetches in the extended card.
- A2A Task States and Operations: What Each State Means for an Orchestrator The eight A2A task states, the eleven operations that act on tasks, the difference between interrupted and terminal states, and an inference-labelled handler matrix for an orchestrator.
- A2A JSON-RPC vs gRPC vs REST: What Differs Between the Three Bindings The three A2A protocol bindings (JSON-RPC, gRPC, HTTP+JSON/REST): what the specification keeps identical, what differs on the wire, and an inference-labelled guide to picking one.
- A2A Authentication Schemes: Which to Declare in Your Agent Card The five security scheme families an A2A Agent Card can declare (API key, HTTP auth, OAuth 2.0, OpenID Connect, mutual TLS), an inference-labelled rule for choosing one, and how a client handles auth-required tasks.
- Credential Propagation Across Agent Hops: Exchange, Audience and Depth How to carry authority through a chain of delegating agents: why forwarding a token fails, per-hop RFC 8693 exchange with act and may_act, RFC 8707 audience binding, a worked sequence and a failure walk-through.
- How to Verify a Remote A2A Agent Before Delegating What a signed Agent Card proves and does not, how domain, key and ERC-8004 identity differ, where Web Bot Auth fits, and why card text and returned artifacts are untrusted input, ending in an ordered checklist.
- How Do Agents Discover A2A Agents Without a Standard Registry? The three discovery strategies in the A2A documentation, why the spec prescribes no registry API, what vendor registries fill the gap, and how to choose between a well-known URI, a registry and direct configuration.
- Migrate A2A v0.3 to v1.0: An Ordered Checklist for Clients and Servers An ordered checklist for moving an A2A client or server from v0.3 to v1.0: the A2A-Version header rule, method names, Part shape, a runnable grep check, and symptom-to-cause pointers.
- Does Your Agent Framework Really Support A2A? How to Read the Claim and What to Test 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.
- Failed or Rejected Remote A2A Task: Retry, Degrade or Surface? How to decide what happens after a remote A2A task ends badly: the side-effects test that splits failed into retry or surface, why rejected is not a retry case, why input-required is not a failure, and a structured result for the caller.
- A2A Production Launch Checklist: Gates to Pass Before You Ship A go/no-go checklist for launching A2A agent-to-agent delegation, one line per gate, each pointing to the article that owns the detail: need, card, states, binding, auth, trust, versioning, failure.