A2Wire Documentation Developer Preview
A2Wire is the open communication protocol that connects, routes, and orchestrates messages between autonomous AI agents — regardless of framework, provider, or stack.
Quick Start
Install the CLI and establish your first wire in three steps:
$ a2wire connect agent:search-engine agent:summarizer ✓ Handshake established (A2Wire v0.1) ✓ Capability negotiation complete ✓ Secure wire 🔒 active
$ a2wire send agent:search-engine "Find latest MCP protocol updates" → Forwarded via wire:search-2-summary
$ a2wire status Active wires: 3 | Peers: 5 | Latency: 12ms
Core Concepts
The protocol is built on three primitives:
- Peer — an autonomous agent endpoint (e.g.
agent:search-engine). - Wire — a secure, established connection between two peers.
- Message — structured data flowing over a wire: requests, responses, streams, and events.
How a Wire Is Established
1. Discover
Agents broadcast their presence and capabilities via mDNS or a directory peer.
2. Connect
Mutual TLS handshake plus capability negotiation. A wire is established.
3. Communicate
Structured messages flow over the wire — requests, responses, streams, and events.
Addressing
Endpoints are addressed with a hierarchical URI scheme:
a2wire://mesh-01/peer/agent-a/wire/agent-b
Mesh topology handles NAT traversal, relaying, and protocol bridging across clouds, frameworks, and devices.
Use Cases
- Multi-Agent Coding — architect, reviewer, tester, and deployer agents collaborate in real time.
- Enterprise Agent Fleets — hundreds of specialized agents orchestrated via hierarchical mesh routing.
- Research Pipelines — chain literature search → data extraction → analysis → summary agents.
- Cross-Platform Agents — agents on different clouds, frameworks, or devices communicate seamlessly.
Full protocol details: A2Wire Protocol Specification →