← Back to concept explainers

Concept Fable

Agent communication protocol

Conclusion first:Agent Communication Protocol is a protocol or language that defines the message format, semantics, and interaction rules between agents. It not only specifies fields but also expresses communication intent, such as request, notification, commitment, refusal, query, delegation, and confirmation. Enterprise multi-agent systems need communication protocols to reduce ambiguity, support state tracking, permission control, error handling, and auditing; otherwise, natural language messages can easily mix facts, requests, and authorization together.

Agent Communication Protocol · Communication

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

Fable

The day the messenger learned to state intent clearly

In the northern territory there were three government offices: the warehouse managed grain, the post station managed carts, and the city gate managed passage. In the past, each sent its own messengers on errands; with short messages and few matters, familiar faces were enough to get things done. Later, the trade routes expanded to more than a dozen cities, messengers multiplied, the city gate could not understand the warehouse's code words, and the post station could not guess the credentials the tax office required.

The first mishap happened with a cart of medicinal herbs. The warehouse messenger said 'please release it,' and the city gate thought it was merely asking whether it could pass; the post station thought it had already been stamped and arranged for the driver to set off overnight. The next day the herbs were seized at the border checkpoint, and all three places said they were not at fault, because each had acted according to local wording.

The city lord first had the messenger write in more detail. The notes grew longer, but the misunderstandings didn't disappear. Some words were requesting a reply, some were assigning tasks, some were just reporting status; without a fixed format, the recipient still had to guess the speaker's identity, purpose, next step, and receipt method.

The old secretary then convened all the government offices and established a set of standard correspondence. Every letter had to specify the sender, recipient, category of matter, required action, deadline, credentials, and who to reply to on failure. Routine inquiries, formal commissions, result reports, and exception requests each had different seals.

At first the messenger found it troublesome, feeling that a familiar phrase had been split into many cells. But the next time the medicinal materials were delayed by rain, the relay station sent back a letter saying "cannot execute on schedule," and the warehouse immediately reassigned a backup vehicle. The city gate also knew that the original clearance order had not been completed and did not stamp it again.

Later, new cities joined the trade route, and as long as they handled matters according to this set of letters, they could collaborate with the old yamen. The city lord then understood: once there are many messengers, what truly matters is not who runs fastest, but that everyone expresses identity, intent, status, and responsibility boundaries in the same way.

Later the kingdom established a river patrol office. The old yamen did not retrain all the messengers; it simply registered the new office's identity, acceptable matters and receipt format in the letter book. On its first day, the river patrol office could request sandbags from the warehouse and ask the city gate to close the bridge, and no one had to guess how to respond.

The king also retained penalty clauses: if a letter lacked items or a receipt, the receiving office could return it; if the delegation was expanded without authorization, the sending office had to bear the consequences. The common language thus shifted from courtesy to collaboration rules, giving cross-departmental assignments a checkable contract.

Reveal

This story is about: Agent communication protocols

Agent Communication Protocol is a protocol or language that defines the message format, semantics, and interaction rules between agents. It not only specifies fields but also expresses communication intent, such as request, notification, commitment, refusal, query, delegation, and confirmation. Enterprise multi-agent systems need communication protocols to reduce ambiguity, support state tracking, permission control, error handling, and auditing; otherwise, natural language messages can easily mix facts, requests, and authorization together.

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

  • Different messengers: different agents or service roles
  • Ordinary chat-style messaging: natural-language messages lacking a protocol
  • Possible: semantically unclear responses
  • Notification mistaken for approval: communication intent and authority conflated
  • Communication protocol: Agent Communication Protocol
  • Intent type and task ID: message semantics and state association
  • Final insight: Agent communication protocols turn messages into executable, auditable collaborative actions

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.

FIPA ACLKQMLStructured dialogueA2A (Agent-to-Agent)
京ICP备2026014272号