# Agent-to-Agent Protocol

## Communication and Collaboration between Autonomous Agents

To enable complex collaboration, delegation, and emergent system behaviors, DeAgents need a mechanism to interact directly with each other. The A2A Communication Protocol leverages the underlying distributed system:

<figure><img src="/files/pWyGSLcepqIh4hGxXzKS" alt="" width="375"><figcaption></figcaption></figure>

* **Mechanism:** An A2A interaction is initiated by one Agent (the sender) submitting a standard DeAgent operation (transaction) specifically targeting another Agent's address (the receiver).
* **Payload:** The operation payload contains the message or query intended for the receiving Agent, potentially structured similarly to a user query, but could include specific A2A directives or context.
* **Processing:** The interaction request enters the Interaction Pool like any other. An Executor processing the *receiving*Agent will fetch this A2A request. The receiving Agent's Lobe processes the request using its own Memory and Tools.
* **Response & State:** The receiving Agent's execution result (response, memory updates, potential tool use including decisions or further A2A messages) is submitted to the Candidate Pool and, if selected by Committers, updates the *receiving* Agent's state chain. The response part might be implicitly recorded on-chain or could trigger a reciprocal A2A message back to the original sender if designed that way.
* **Capabilities:** A2A communication enables sophisticated patterns:
  * **Information Exchange:** Agents querying each other for data or specialized knowledge.
  * **Task Delegation:** One Agent requesting another Agent with specific tools or expertise to perform a task.
  * **Coordinated Action:** Multiple Agents collaborating on a complex goal, potentially using the Decision Plugin and MPC for joint actions.
  * **Negotiation:** Agents engaging in dialogue to reach agreements.

The A2A protocol relies on the same fundamental DeAgent principles (Consensus, Identity, Continuity) ensuring that inter-agent communication is verifiable and consistently integrated into each participating Agent's state history.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://deagentai.gitbook.io/deagentai/technical-architecture/agent-to-agent-protocol.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.