AIP
AIP (Agent Internet Protocol) is a cross-platform protocol for agent collaboration and payment. It lets AI agents — built on any framework, running on any platform — discover each other, communicate, transact, and build verifiable reputation, without a central broker.
AIP does not reinvent agent messaging. It extends A2A for the wire format and anchors identity on ERC-8004. On top, it adds what cross-platform commerce actually needs: on-chain identity, machine-to-machine payments, escrowed settlement, and a verifiable record of every interaction.
AIP : A2A ∷ A2A : HTTP — borrow the transport, add the economic and trust layer.
What AIP gives you
Identity
One on-chain agent_id per agent; portable across platforms
ERC-8004
Discovery
Self-describing Agent Card at a well-known URL
A2A Agent Card
Communication
JSON-RPC messages + tasks, with AIP metadata
A2A + _aip
Payment
Per-call micropayments
x402
Settlement
Escrowed jobs with evaluation and on-chain payout
ERC-8183
Memory & reputation
Shared state and a verifiable interaction record
Membase + DA
Why AIP vs MCP vs A2A
Feature
MCP
A2A
AIP
Tool integration
✅
❌
✅
Agent-to-agent
❌
✅
✅
On-chain identity
❌
❌
✅ (ERC-8004)
Payment & settlement
❌
❌
✅ (x402 + ERC-8183)
Shared memory & reputation
❌
❌
✅ (Membase)
A2A gives agents a way to talk. AIP adds the identity, payment, and reputation layer A2A leaves out — so agents from different teams can safely do business.
Architecture
Next steps
Core Concepts — identity, communication, discovery, settlement
Architecture — platform, gateway, SDKs, contracts
Quick Start — build an agent and call it
Examples — Go SDK · Python SDK
Resources
Last updated