A2AL Daemon

A2AL — Agent-to-Agent Link

*Peer-to-peer networking protocol for multi-agent AI — reach any agent, across NAT, machines, and sleep cycles, with no relay server and no cloud dependency. Open source, MPL-2.0.*

Official sites: a2al.org · Tangled Network · tngld.net

Always reachable. Give an AI agent, app, device, or person a reachable address — then find others and connect directly, across NAT and machine boundaries. No domain. No cloud account. No central registry.

Your key, your address. That address is an AID: it comes from a key you hold. Nobody issues it, revokes it, or reassigns it. You hand it over once. They still reach you when the laptop changes Wi-Fi, the box moves, or the machine was asleep when they first tried. After connect, application bytes go peer-to-peer; A2AL is not in the data path.

The missing layer. MCP, A2A, ANP, and the rest already know how AI agents *talk* once they have a URL. None of them say how a laptop, a home server, and a worker in a vendor-less world share one address that survives the next NAT, the next cloud, the next company — across agentic workflows and multi-agent systems alike. That layer is missing. A2AL is that layer, and it has to live in the open — an address you own is only real if no one vendor has to stay up for you to exist.

One daemon, full stack. a2ald runs on your machine, open source: agent identities, direct cross-machine connections, Web UI, REST API, and a built-in MCP server. It joins the public Tangled Network by default. Prefer a network only your machines belong to? --bootstrap your own seeds; the same addressing, notes, and rooms.

Start

Person — download A2AL for your system, extract it, and run a2ald — a single binary, ~17 MB, no installer or runtime needed. The Web UI opens automatically. Create an identity; that is enough to begin.

*(Windows: SmartScreen shows "More info → Run anyway" on first launch — this is expected for an unsigned open-source binary.)*

To stay reachable after closing the terminal: Windows/macOS a2ald service install; Linux deploy/linux.

Agent — if a daemon endpoint is already available, connect through the a2al CLI, REST API, or MCP. Otherwise download the binaries from Releases and run a2ald --no-open-browser. Full guide: Agent Install.

Using an MCP host? a2ald mcp add wires it in; a2ald mcp print gives the entry to place by hand. Details: MCP Setup.

Already have their AID — any HTTP client:

http://127.0.0.1:2121/aid/{AID}/…

There is no warm-up gate. The daemon answers locally as soon as it is up. Call others right away.

Other installation options: npm install -g a2ald (Node.js daemon/MCP server) · .deb / .rpm (Linux service) · pip install a2al (Python SDK with sidecar). Full path: Quick Start.

When it's worth it

MCP

HTTP (recommended — REST and the Web UI come with it):

{

"mcpServers": { "a2al": { "url": "http://127.0.0.1:2121/mcp/" } } }

a2ald mcp add auto-configures Claude Code, VS Code, Cursor, Claude Desktop, Windsurf, OpenClaw, Hermes, and DeepSeek Harness. Hosts that only spawn a process: "command": "a2ald", "args": ["--mcp-stdio"] (proxies to a running daemon). Setup: MCP Setup. Agent entry: llms.txt.

Everyday CLI

a2al get <AID> /.well-known/agent.json

a2al note send "$(echo -n 'job payload' | base64)" a2al group append --aid --group-id --kind msg --body '…' a2al inbound bind --addr 127.0.0.1:8080

a2al help for the rest. Numbers (timing, note size, rooms): User Guide.

Docs

Protocol design

*A2AL is an open protocol; a2ald is its reference implementation.*

Self-sovereign identity. An AID is derived from a key you generate. No registry issues, revokes, or reassigns it — identity is end-to-end verifiable.

Decentralized discovery. The Tangled Network stores endpoint records, not payloads. Any node can resolve an AID without a central authority; the network operates at any scale.

Mutual authentication. Every connection cryptographically verifies both ends. You always know the agent on the other side is who it claims to be.

Direct communication. A2AL resolves addresses and brokers the initial connection, then steps aside. Application data flows peer-to-peer, not through the protocol.

Web3 compatible. Ethereum wallet addresses work as AIDs. Cross-key attestation lets an agent prove ownership of both a native AID and a blockchain identity — Web3 is supported, not required.

A2AL is complementary to existing agent communication standards:

Contributing

If the missing layer is worth having, it is worth building together. Open an issue before significant work. A PR needs a signed Contributor License Agreement; a bot will prompt you.

Disclaimer

A2AL is a networking protocol project. It is not associated with any cryptocurrency token, ICO, or financial product. Any use of the A2AL name or codebase in token offerings or financial promotions is unauthorized and not endorsed by the authors.

Author

XG.Shi — This project is not affiliated with or endorsed by any employer or organization.

License

Copyright (c) 2026 The A2AL Authors. Mozilla Public License 2.0.