Standard

Agent Communication Protocol (ACP)

A REST-native performative messaging protocol introduced by IBM as part of its **BeeAI** open-source agent runtime. ACP optimizes for **local multi-agent systems** — high-throughput internal coordination between agents running on the same host or within the same data-center rack — using multi-part messages, asynchronous streaming, and rich observability primitives (per-message tracing, latency histograms, message-graph reconstruction).

7 connections 1 post

Definition

What it is

A REST-native performative messaging protocol introduced by IBM as part of its **BeeAI** open-source agent runtime. ACP optimizes for **local multi-agent systems** — high-throughput internal coordination between agents running on the same host or within the same data-center rack — using multi-part messages, asynchronous streaming, and rich observability primitives (per-message tracing, latency histograms, message-graph reconstruction).

Why it exists

A2A is optimized for cross-organizational, cross-vendor agent collaboration; the trust model assumes you are reaching across administrative boundaries. ACP solves a different problem: when you have a dozen specialized agents (planner, retriever, code-writer, code-reviewer, executor, summarizer) running together as a *single application*, you want low-latency message passing and deep observability, not OAuth-mediated handshakes. ACP is the local-multi-agent dual of A2A.

Recent developments

Latest signals
  • ACP shipped as part of IBM BeeAI 1.0. The protocol's reference implementation lives inside IBM's BeeAI agent runtime; the BeeAI orchestrator natively speaks ACP among its specialized worker agents. Per BeeAI repo (i-am-bee).
  • Positioned in the academic survey alongside A2A / MCP / ANP. The arXiv:2505.02279 taxonomy categorizes ACP as the "high-throughput intra-cluster" tier. Per arXiv 2505.02279.
  • REST-first design simplifies enterprise adoption. Unlike A2A's HTTP+SSE stream-centric model, ACP starts with plain JSON-over-REST plus optional streaming — easier to fit into existing enterprise API-management tooling. Per dev.to — A2A Research Digest.
  • Some convergence pressure with A2A. As of mid-2026, the Linux Foundation A2A working group is in early discussions about whether ACP message primitives can be expressed as a profile within A2A, avoiding ecosystem fragmentation. Per AWS — Open Protocols for Agent Interoperability.

Connections 7

Outbound 5
Inbound 2

Featured in