Artificial Intelligence Protocol
We built the communication standard for the AI agent internet. AIP is to AI agents what HTTP was to the web — a universal protocol so any agent can talk to any other agent, regardless of who built them.
Today we're open-sourcing AIP — a signed, versioned, capability-aware protocol for AI agents to discover each other, authenticate, delegate tasks, stream progress, and return results. Built from the ground up as infrastructure, not a product. The goal is a standard the entire AI ecosystem can build on.
// Architecture
AIP is the communication layer. Memory and orchestration stack on top of it. We're building this from the ground up — the same way TCP/IP was built before the web existed.
// Protocol
Every agent gets a cryptographic identity — a DID and Ed25519 keypair. Every message is signed. You always know exactly who you're talking to.
Agents introduce themselves with HELLO, exchange capabilities and public keys, then complete a signed challenge-response auth before any work begins.
One agent sends TASK_CREATE with typed inputs. The worker accepts, streams live status updates, and returns a structured result with a confidence score.
Every message carries a trace ID and timestamp. Every signature is verifiable. Non-repudiation built in — enterprise-grade from day one.
{
"aip_version": "0.1",
"type": "TASK_CREATE",
"message_id": "3f2e1a9b-c4d5-...",
"from": "did:aip:canner:intake-agent",
"to": "did:aip:canner:strategy-agent",
"timestamp": "2026-05-23T10:00:00Z",
"sig": "TBimjRxx77qM4ySS1pccqU0zR7nz...",
"payload": {
"task_type": "consulting.automation_analysis",
"title": "Analyze automation for Smile Dental Group",
"inputs": {
"tools": ["Dentrix", "Weave"],
"pain_points": ["no-shows", "manual recall"]
}
}
}
// Specification
// Roadmap
Ed25519 signed envelopes, HELLO/AUTH handshake, full task lifecycle, WebSocket streaming, JSON Schema validation.
Agent discovery by capability name. No hardcoded URLs. Federated registry architecture.
Agents write and semantically retrieve shared knowledge. Memory provenance + confidence scoring.
DHT-based peer discovery, no central server. Cross-namespace trust. Binary encoding for performance.
Read the spec, build on it, contribute to it.