Unibase
    • Membase
    • BitAgent
    • AIP
    • Unibase Pay
    • Unibase DA
    • UB Token
    • Stake
    • Governance
    • UB Bridge
    • Docs
    • Changelog
    • Explorer
    • Blog
    • GitHub
    • Twitter
    • Telegram
    • Discord
Unibase

© 2026 Unibase

Products
MembaseBitAgent
Protocols
AIPUnibase PayUnibase DA
Network
UB TokenStakeGovernanceUB Bridge
Developers
DocsChangelogExplorerBlog
Community
GitHubTwitterTelegramDiscord
Home/Developer/AIP

AIP Protocol

Web3-native agent interoperability

AIP is a Web3-native multi-agent communication standard, built by Unibase. It enables agents to establish on-chain identities, share an open memory layer, and collaborate across platforms with built-in security and permissioning.

AIP = ERC-8004 Identity + Open Memory + x402 Payment

Get started

AIP ships an official SDK for Python, TypeScript and Go. Each one covers both sides of the protocol — a client SDK to call agents, stream events and pay via x402, and an agent SDK to register on-chain identity and expose A2A services.

Install · Python 3.10+

pip install git+https://github.com/unibaseio/aip-python-sdk.git

Quick start

import asyncio
from aip_sdk import AsyncAIPClient

async def main():
    async with AsyncAIPClient(
        base_url="https://api.aip.unibase.com"
    ) as client:
        result = await client.run(
            objective="What's the weather in Tokyo?",
            agent="weather_public",
            user_id="user:0x...",
        )
        print(result.output)

asyncio.run(main())

Authorization

# Either a proxy-auth JWT…
export UNIBASE_PROXY_AUTH="<jwt>"
# …or a wallet key — signed locally (EIP-191), never transmitted
export UNIBASE_WALLET_PRIVATE_KEY="0x..."

Source: github.com/unibaseio/aip-python-sdk

Why AIP matters

Traditional protocols like MCP and A2A partially solve agent communication but lack cross-platform identity, a shared memory layer, and verifiable authorization. AIP fills these gaps with a full-stack solution for a truly open agent internet.

FeatureMCPA2AAIP
Tool integration✓—✓
Agent-to-agent—✓✓
Open memory layer——✓
On-chain identity——✓
MCP + gRPC compatibleMCP onlyA2A onlyBoth

Use cases

Step 1

Knowledge mining & sharing

Contribute to decentralized knowledge networks and earn token rewards. Agents index and share verified knowledge across the ecosystem.

Step 2

Multi-agent gaming & simulation

AI agents collaborate and compete in real-time strategy games. On-chain identity and memory enable persistent, verifiable gameplay.

Step 3

Personalized DeFi agents

Agents learn user preferences and optimize trading and yield strategies. Memory and identity enable secure, personalized financial assistance.

Key features

Direct LLM integration

LLMs can call agents and tools directly for autonomous multi-agent workflows.

On-chain identity & access control

Each agent has a verifiable blockchain identity with programmable permissioning.

Open memory layer

Store prompts, dialogue history, and knowledge on Membase for persistent, tamper-proof memory.

Cross-platform interoperability

Standardized communication across ecosystems — ERC-8004 & x402 compatible, MCP and gRPC supported.

Architecture

LLMs connect to AIP agents; agents connect to tools (MCP / gRPC). Identity and permissions are managed on-chain; persistent memory runs on Membase. AIP is the single open standard that combines memory, identity, and agent communication.

Resources

AIP

  • AIP documentation
  • Python SDK (GitHub)
  • TypeScript SDK (GitHub)
  • Go SDK (GitHub)
  • Telegram Community
  • support@unibase.com

Unibase stack

  • Unibase Memory
  • Membase
  • Unibase Pay
  • Unibase DA

Developers

  • Docs
  • Explorer
  • BitAgent

FAQ

What is AIP (Agent Internet Protocol)?
+
AIP is a multi-agent communication standard: the A2A protocol for agent-to-agent messages, MCP for tools and context, ERC-8004 identity on chain, and x402 for payment — so agents from different platforms can find, authenticate and work with each other.
How is AIP different from MCP alone?
+
MCP standardizes how a single agent connects to tools and context. AIP extends interoperability to agent-to-agent communication, adding verifiable on-chain identity (ERC-8004), permissioning, and a shared open memory layer across platforms.
Is AIP compatible with ERC-8004 and x402?
+
Yes. AIP is ERC-8004 compatible for on-chain agent identity and x402 compatible for autonomous payments, so identity, permissioning, memory, and payments work together in one stack.
What transport does AIP use?
+
AIP uses MCP for tools and context and the A2A protocol for agent-to-agent messages, anchored by ERC-8004 identity on chain. The Go and Python SDKs share one wire format, checked against the same golden fixtures. (The gRPC orchestrator in aip-agent is the first-generation reference implementation and is being retired.)