Editing
Agent Communication Protocol
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Infobox protocol | name = Agent Communication Protocol | developer = [[wp:IBM|IBM]]/BeeAI β [[wp:Linux Foundation|Linux Foundation]] | status = Stable | first_published = 2025 | transport = [[wp:HTTP|HTTP]], Local IPC | encoding = [[wp:JSON|JSON]] | license = [[wp:Apache License|Apache 2.0]] | repository = https://github.com/ibm/acp }} 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. == Overview == 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. === Design philosophy === * '''Local-first''' β Optimized for on-device and edge deployments * '''Low latency''' β Minimal network overhead for real-time coordination * '''Privacy-preserving''' β Data stays local by default * '''Offline-capable''' β Full functionality without internet access == Architecture == ACP defines a decentralized agent environment with: * '''Local discovery''' β Agents find each other via local broadcast or shared registry * '''Direct messaging''' β Peer-to-peer communication without central routing * '''State synchronization''' β Coordinated state management across agents == Use cases == ACP is particularly suited for: * Industrial IoT and edge computing * Healthcare environments with strict data sovereignty requirements * Embedded systems and robotics * Air-gapped or offline deployments == Comparison with other protocols == {| class="wikitable" |- ! Aspect !! ACP !! [[Agent-to-Agent Protocol|A2A]] !! [[Model Context Protocol|MCP]] |- | Primary focus || Local coordination || Cloud collaboration || Tool integration |- | Network requirement || Optional || Required || Required |- | Latency || Ultra-low || Variable || Variable |- | Privacy || Local by default || Cloud-dependent || Tool-dependent |} == See also == * [[Agent-to-Agent Protocol]] * [[Model Context Protocol]] * [[Agent Network Protocol]] == References == {{Reflist}} == External links == * [https://github.com/ibm/acp GitHub repository] [[Category:Communication Protocols]] [[Category:Agent Communication]] [[Category:IBM Specifications]]
Summary:
Please note that all contributions to secondtruthLabs Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
secondtruthLabs Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Templates used on this page:
Template:Infobox protocol
(
edit
)
Template:Reflist
(
edit
)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
Edit source
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information