← Back to concept explainers

Concept Fable

Agent-to-Agent protocol

Conclusion first:Agent2Agent, A2A refers to the protocol direction for interoperability and communication between different Agents, enabling one Agent to discover another Agent’s capabilities, initiate tasks, pass context, receive status, and process results. It focuses on collaboration boundaries across systems, vendors, and organizations. In enterprise scenarios, the value of A2A lies in enabling specialized Agents to be invoked like services while preserving identity, permissions, task status, error handling, and human approval mechanisms.

Agent2Agent, A2A · Agent protocol

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

The pass that two cities could finally mutually recognize

Both Hedong City and Hexi City had capable operations teams. The east city excelled at checking ship schedules, the west city at inspecting goods. If a caravan wanted to complete a cross-city delivery, it had to send people back and forth between the two sides repeatedly. Early messaging relied on natural language. The east said “goods are ready,” but the west did not know whether they were inspected, loaded, or merely available on the books. The west said “credentials required,” but the east did not know which credentials were needed.

The two cities first wrote their own manuals. The manuals grew thicker and thicker, but could not prevent misunderstandings. Each service team had its own terms, states, and failure-reporting methods.

During a rush order, the East City ship inspection team thought the task was complete, while the West City cargo verification team was still waiting for a batch number. Neither side was slacking, yet the message could not be reliably understood by the other.

The city lords created a pass card: identity, what can be done, what papers are required, how far it has progressed, the reason for errors, the receipt stamp, and permission boundaries, all expressed in fixed fields.

From then on, the East City could send standard commissions to the West City, and the West City could clearly declare what it could do, what it lacked, and whether it needed a superior's seal. The service teams did not have to expose their own internal rules and could still hand off reliably.

The two cities tried assigning fixed messengers, but whenever a messenger changed shifts, the old codes failed again. In the end, they made the pass into a unified format: task, status, credentials, next step, and failure reason each occupied one cell; whoever received the pass could know what they should do.

After the unified pass was piloted, caravans took far fewer wasted trips. The East City office team knew which credential West City needed, and West City could understand how far East City's delivery had progressed. Both sides still kept their own crafts, but cross-city collaboration no longer relied on guessing each other's dialect. Later, when urgent orders came again, the two cities no longer sent a dozen trips to explain the same thing. The fields on the pass let tasks be accepted, tracked, and returned; collaboration became faster because misunderstandings decreased.

The caravan discovered that the real change happened after the shared protocol was established: the two cities could discover, commission, accept, and reject each other. Without this protocol, even the smartest team would exhaust its patience at the handoff point.

Reveal

This story is about: Agent-to-Agent protocols

Agent2Agent, A2A refers to the protocol direction for interoperability and communication between different Agents, enabling one Agent to discover another Agent’s capabilities, initiate tasks, pass context, receive status, and process results. It focuses on collaboration boundaries across systems, vendors, and organizations. In enterprise scenarios, the value of A2A lies in enabling specialized Agents to be invoked like services while preserving identity, permissions, task status, error handling, and human approval mechanisms.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • East River City and West River City: Agents in different systems, vendors, or organizations
  • Natural language messaging: unstructured agent-to-agent collaboration
  • The manual gets thicker and thicker: patches for inconsistent interface semantics
  • Batch number misunderstanding: missing state and input contracts
  • Pass: standard messages and capability descriptions in the A2A protocol
  • Declare what it can do and what it needs: Agent discovery and task contract
  • Final insight: what A2A needs to solve is interoperable task collaboration between Agents

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

multi-agenthandoffinteroperability

Bring back real work

If you want Agents in different systems or roles to hand off tasks, first define capability discovery, context, state, permissions, errors, and responsibility boundaries, then decide whether an A2A interface is needed.

京ICP备2026014272号