http://wiki.secondtruth-labs.com/index.php?action=history&feed=atom&title=Agent_Communication_Protocol
Agent Communication Protocol - Revision history
2026-06-21T09:06:43Z
Revision history for this page on the wiki
MediaWiki 1.43.0
http://wiki.secondtruth-labs.com/index.php?title=Agent_Communication_Protocol&diff=10&oldid=prev
imported>Import at 16:36, 31 December 2025
2025-12-31T16:36:32Z
<p></p>
<p><b>New page</b></p><div>{{Infobox protocol<br />
| name = Agent Communication Protocol<br />
| developer = [[wp:IBM|IBM]]/BeeAI → [[wp:Linux Foundation|Linux Foundation]]<br />
| status = Stable<br />
| first_published = 2025<br />
| transport = [[wp:HTTP|HTTP]], Local IPC<br />
| encoding = [[wp:JSON|JSON]]<br />
| license = [[wp:Apache License|Apache 2.0]]<br />
| repository = https://github.com/ibm/acp<br />
}}<br />
<br />
The '''Agent Communication Protocol''' ('''ACP''') is an open standard for local-first agent coordination with minimal network overhead. Originally developed by [[wp:IBM|IBM]]'s BeeAI project, ACP is now part of the [[wp:Linux Foundation|Linux Foundation]] and focuses on environments where low latency, privacy, and offline operation are critical.<br />
<br />
== Overview ==<br />
<br />
While protocols like [[Agent-to-Agent Protocol|A2A]] focus on cloud-based agent collaboration, ACP is designed for edge computing and local-first environments. It enables agents to coordinate within a single system or local network without requiring constant internet connectivity.<br />
<br />
=== Design philosophy ===<br />
<br />
* '''Local-first''' – Optimized for on-device and edge deployments<br />
* '''Low latency''' – Minimal network overhead for real-time coordination<br />
* '''Privacy-preserving''' – Data stays local by default<br />
* '''Offline-capable''' – Full functionality without internet access<br />
<br />
== Architecture ==<br />
<br />
ACP defines a decentralized agent environment with:<br />
<br />
* '''Local discovery''' – Agents find each other via local broadcast or shared registry<br />
* '''Direct messaging''' – Peer-to-peer communication without central routing<br />
* '''State synchronization''' – Coordinated state management across agents<br />
<br />
== Use cases ==<br />
<br />
ACP is particularly suited for:<br />
<br />
* Industrial IoT and edge computing<br />
* Healthcare environments with strict data sovereignty requirements<br />
* Embedded systems and robotics<br />
* Air-gapped or offline deployments<br />
<br />
== Comparison with other protocols ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Aspect !! ACP !! [[Agent-to-Agent Protocol|A2A]] !! [[Model Context Protocol|MCP]]<br />
|-<br />
| Primary focus || Local coordination || Cloud collaboration || Tool integration<br />
|-<br />
| Network requirement || Optional || Required || Required<br />
|-<br />
| Latency || Ultra-low || Variable || Variable<br />
|-<br />
| Privacy || Local by default || Cloud-dependent || Tool-dependent<br />
|}<br />
<br />
== See also ==<br />
<br />
* [[Agent-to-Agent Protocol]]<br />
* [[Model Context Protocol]]<br />
* [[Agent Network Protocol]]<br />
<br />
== References ==<br />
<br />
{{Reflist}}<br />
<br />
== External links ==<br />
<br />
* [https://github.com/ibm/acp GitHub repository]<br />
<br />
[[Category:Communication Protocols]]<br />
[[Category:Agent Communication]]<br />
[[Category:IBM Specifications]]</div>
imported>Import