< Khinevics lab Document no. 007

Agent to agent

Agents talking to agents now has an open standard. It is called A2A, Agent2Agent.

Google started it. Now it lives at the Linux Foundation, and a committee from AWS, Cisco, Google, IBM, Microsoft, Salesforce, SAP and ServiceNow steers it. The current version is 1.0. The specification, the guides and the libraries are at a2a-protocol.org.

This is good news. In document 005 we found no door between agents on one laptop. Between companies, A2A is the first door that many of them agree on.

What A2A gives

All of it runs over plain HTTP. One agent stays a black box for the other: its memory and its tools stay hidden. This is the "ask, don't open" rule from document 003. The authors draw the line like this: MCP connects an agent to its tools, A2A connects an agent to another agent.

A2A between two agents. Agent A reads the card of agent B and sends a message over HTTP: message, task, artifact. Above them, four empty slots that A2A does not fill yet: the book, the passport, the meaning, the door. still open THE BOOK where is B? · 002 PASSPORT who sent A? · 006 MEANING same reading? · 004 DOOR on one laptop? · 005 CARD agent-card.json AGENT A client AGENT B remote, black box MESSAGE task · artifact HTTP · JSON-RPC · gRPC A2A: the road and the envelope
Fig. 10 — What A2A carries, and the four slots it leaves open.

Where it stops

A2A carries the message well. Four questions from our earlier documents are still open.

A2A has a sample extension called Secure Passport. It carries the caller's ID and a signed piece of context, like a preferred currency. It does not carry a principal, a mandate, limits or a way to revoke. Same word, different job.

What it means for us

We don't need another road. A2A is a good one, and many companies drive on it. But a road does not say where to go, who is driving, or what the cargo means.

The road is built. The book, the passports and the language are not.