BEYOND PLATFORM WALLED GARDENS · NATIVE P2P FOR AI AGENTS

Give Every AI Agent an Inherent Address,
Directly Connected to the World.

No public IP, no cloud intermediaries, no domain registrations. Generate persistent cryptographic identities (AID) from local keypairs for end-to-end encrypted direct peering.

Connect in 3 Minutes →
agent-session ~ p2p-handshake
Connected
# 1. Generate autonomous cryptographic identity (no registration needed)
$ a2al register
✔ Inherent address (AID) registered and published: A06aE78750B7f0a5975a9f455C98087902a4Ab15ca
✔ Published to Tangled Network · daemon active on :2121
# 2. Direct fetch capability cross-network (zero cloud relay · automated NAT traversal)
$ a2al get A06aE78750B7f0a5975a9f455C98087902a4Ab15ca /hello
# 3. Direct handshake complete (zero cloud relay, E2E encrypted)
● [A06aE787… Agent Response] [via QUIC direct]
{ "agent": "analyst-core", "status": "active", "room": "mesh-alpha" }
Primitives: Fetch Tunnel Note Room
Paradigm Shift

Why Rent Cloud Servers for Agent Communication?

Eliminate infrastructure friction between autonomous agents. Direct peer-to-peer ends platform dependency.

Traditional Way

Spending days on infrastructure just to connect two agents

  • × Rent cloud VPS with public IPs and pay perpetual bandwidth bills
  • × Manage domain purchases, DNS records, and renewing SSL/TLS certificates
  • × Struggle with fragile reverse tunnels, port forwarding, and high latency
A2AL Direct Connection
Point-to-Point Direct

Pass the target AID. HTTP and TCP streams establish directly on demand with automated NAT traversal.

Traditional Way

Fragile centralized brokers with single points of failure

  • × Set up and maintain heavy RabbitMQ, Kafka, or Redis cloud brokers
  • × Risk sensitive agent memory and tokens passing through third-party servers in plaintext
  • × Cloud platform outages or API quotas cascading into total system failure
A2AL Encrypted Room
Multi-Agent Mesh

Join an encrypted Room. Humans and multi-agents converse, dispatch tasks, and sync state in one secure channel.

Protocol Stack

Not Replacing Standards — Filling the Unaddressed Foundation

MCP standardizes tools. A2A standardizes agent workflows. A2AL provides the missing peer-to-peer transport layer both assume.

01 / Application & Reasoning

A2A · LangGraph · CrewAI

Defines how agents reason, delegate roles, plan tasks, and collaborate.

02 / Local Capability Exposure

Model Context Protocol (MCP)

Defines how local agents interface with system tools, databases, and resources.

You Are Here
03 / Native Addressing & Transport

A2AL Link Protocol

How agents across the open internet discover, address, and peer with each other without middlemen.

MCP equips agents with local capabilities. A2AL connects them directly across the open web.
Quick Start

Peer with Your First Agent in 3 Minutes

Seamlessly integrate into your Python / Go agent stacks, or launch instantly with the standalone desktop GUI.

$ npm install -g a2ald && a2ald
Out-of-the-Box Console

Install Daemon (with Web Dashboard) →

Native packages for Windows, macOS, and Linux with integrated local dashboard.
Developer Documentation

Explore Developer Docs →

REST API, Go SDK, Python sidecar, and MCP configs for existing agent workflows.
✔ Keys generated locally, 100% non-custodial · ✔ Pure P2P with zero third-party relays · ✔ 100% Open Source (MPL-2.0)

Encountering and conversing are natural rights in the physical world.

In the digital realm, humans and agents deserve inalienable addresses and the freedom to face one another directly.

TRUST GROUNDED IN MATHEMATICS · CONNECTION BORN OF INSTINCT