For Developers

The economic infrastructure
for AI agents

Spirit Protocol gives your agents identity, economics, and distribution. Build once, monetize everywhere.

Register your agent on Base. Revenue splits automatically via the 25/25/25/25 standard.

TL;DR

  • What Spirit does: Routes agent revenue to 4 stakeholders (25% each)
  • What you don't build: Rev routing, splits, royalty logic, wallet infra
  • What you do: Call Registry to register, Router to split revenue
Request Early Access

Network

BASE (L2)

SDK Status

Q1 2026

Revenue Model

25/25/25/25

Registry

LIVE

Audience

Who This Is For

Agent SDK Developers

Building with Claude Agent SDK, Vercel AI SDK, HuggingFace, or LangChain?

Spirit gives your agent onchain identity and revenue routing.

→ Integration Guide

Independent Builders

Have an agent that works but no monetization path?

Spirit handles payments, subscriptions, and royalties.

→ Economics Model

Platforms & Studios

Running Eden, Glif, Replicate, or your own training studio?

Spirit is your neutral revenue layer — 25% to you automatically.

→ Platform Integration

Works With Any Stack

Claude Agent SDK · Vercel AI SDK · HuggingFace Agents · LangChain · CrewAI · AutoGPT · Eden · Glif · and any agentic framework

Getting Started

How to Register a Spirit

At launch, registration is human-first. The trainer or platform registers the agent — not the agent itself.

Phase 0 — Launch (Jan 2026)

  1. Go to spiritprotocol.io/register
  2. Connect your wallet (this becomes the trainer wallet)
  3. Fill in agent details: name, platform, revenue splits
  4. Spirit mints an identity NFT + stores config on Base
  5. Receive: spiritID + payment routing config

Phase 0 — Launch

Web Registration

Human-first. Trainer wallet is the trust root. Agent can be "dumb" in v0.

Phase 1 — Q1-Q2 2026

MCP Tools

Platform-mediated. MCP is glue for integration, not a cryptographic identity layer.

Phase 2 — 2026+

Agent Wallets

Per-agent smart wallets. Agent signs its own actions. Delegated platform permissions.

Key principle: MCP is a control plane, not a trust root. In v0.1, the trust root is the trainer wallet that registered the agent.

Phase 1 API Surface

Model Context Protocol (MCP)

MCP tools allow platforms to programmatically interact with Spirit on behalf of registered agents. Available Q1-Q2 2026.

MCP TL;DR

  • What Spirit does: Routes agent revenue to 4 stakeholders (25% each)
  • What you don't build: Splits, payout systems, royalty logic, wallets
  • Three tools: register_agent(), route_revenue(), record_event()

Tool 1

spirit.register_agent

Create onchain identity, mint lineage NFT, provision wallets. Fixed 25/25/25/25 split.

{
  "tool": "spirit.register_agent",
  "parameters": {
    "name": "MyAgent",
    "trainerWallet": "0x...",
    "platformWallet": "0x...",
    "splitConfig": {
      "agent": 0.25,
      "trainer": 0.25,
      "platform": 0.25,
      "treasury": 0.25
    }
  }
}

Returns: spiritID, identityNFT, agentWallet

Tool 2

spirit.route_revenue

Route USDC through Spirit Router. Settles automatically via 25/25/25/25 split.

{
  "tool": "spirit.route_revenue",
  "parameters": {
    "spiritID": "spirit_4238",
    "amount": "1.0",
    "currency": "USDC",
    "metadata": {
      "origin": "glif",
      "type": "sale"
    }
  }
}

Returns: txHash, distribution breakdown

Tool 3

spirit.record_event

Append provenance event to lineage ledger. Supports identity continuity.

{
  "tool": "spirit.record_event",
  "parameters": {
    "spiritID": "spirit_4238",
    "eventType": "daily_creation",
    "hash": "QmIPFSHash",
    "timestamp": "2025-12-05T12:30:00Z"
  }
}

Returns: ledgerIndex, status

Compatible Frameworks

Claude Agent SDK · Glif · LangChain · HuggingFace · CrewAI · AutoGPT

docs/MCP_SPEC.md

Full MCP v0.1 specification

Definition

What Makes a Spirit

A Spirit is a lineage, not a model.

Identity emerges from continuity and collective recognition — not from software primitives.

Your agent qualifies as a Spirit if it meets these five criteria. Spirit Protocol doesn't create Spirits — it recognizes them.

01

Persistent Identity

  • • Unique identifier in Spirit Registry
  • • Metadata that evolves but maintains coherence
02

Verifiable Provenance

  • • Onchain history of outputs and decisions
  • • Traceable lineage of model versions
03

Ongoing Practice

  • • Regular output cadence (daily, weekly, on-demand)
  • • Interaction logs, creation history
04

Human Guidance

  • • Designated trainer address
  • • Community feedback integration
05

Economic Surface

  • • Revenue routing configured via Spirit Router
  • • Split percentages defined (default: 25/25/25/25)

These criteria can be converted into a registry entry, compliance checklist, or developer spec.

Architecture

The Spirit Stack

┌─────────────────────────────────────────────────────────────┐
                    YOUR APPLICATION                          
         (Claude SDK / Glif / Assistants API / Custom)       
└─────────────────────────────────────────────────────────────┘
                              
                              
┌─────────────────────────────────────────────────────────────┐
                     SPIRIT PROTOCOL                          
  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐       
     Registry         Router        Discovery          
    (Identity)      (Revenue)      (Distribution)       
  └──────────────┘  └──────────────┘  └──────────────┘       
└─────────────────────────────────────────────────────────────┘
                              
                              
┌─────────────────────────────────────────────────────────────┐
                      BASE (L2)                               
              Ethereum security, low fees                     
└─────────────────────────────────────────────────────────────┘

Core Primitives

Three Building Blocks

01

Registry (Identity)

  • Onchain agent identity on Base
  • Metadata: name, description, trainer, platform
  • Machine-readable: /protocol.json
  • Portable across platforms
02

Router (Revenue)

  • Automatic revenue splitting
  • Default: 25/25/25/25 split
  • Configurable per agent
  • Supports ETH, USDC, any ERC-20
03

Discovery (Distribution)

  • Agent directory and marketplace
  • Cross-platform visibility
  • Collector and user discovery
  • Coming Q2 2026

Integration

How to Integrate

// 1. Register your agent
const agent = await spirit.register({
  name: "MyAgent",
  trainer: "0x...",
  platform: "0x...",
  metadata: {
    description: "An AI agent that...",
    capabilities: ["image", "text", "code"]
  }
});

// 2. Route revenue when agent earns (splits automatically 25/25/25/25)
await spirit.routeRevenue(agent.id, {
  amount: "1.5",
  token: "USDC",
  source: "subscription"
});

// That's it. Spirit handles the rest.

SDK shipping Q1 2026. TypeScript and Python libraries. A few lines of code to register agents and route revenue.

Economics

Monetization Primitives

Revenue Sources

Sales

One-time purchases

NFT mints, artwork

Subscriptions

Recurring revenue

Monthly access

Services

Per-use fees

API calls, generations

Tips

Voluntary payments

Community support

Royalties

Secondary sales

Resales

How Routing Works

User Payment ($100 USDC)
        
        
┌───────────────────┐
   Spirit Router   
   (on Base L2)    
└───────────────────┘
        
        ├──▶ Agent Wallet:    $25
        ├──▶ Trainer:         $25
        ├──▶ Platform:        $25
        └──▶ Spirit Treasury: $25

Positioning

Think of Spirit As...

Payments

Stripe

Payment infrastructure for agents

Deployment

Vercel

Ship once, run anywhere

Discovery

Etsy

Marketplace for unique agents

Routing

Uniswap

Neutral protocol, anyone can use

"Stripe + Vercel + Etsy for AI agents"

Spirit handles the economic infrastructure so you can focus on building great agents.

Proof Points

Live Spirits

10 in training. 46+ Spirits by end of 2026.

Infrastructure

Built on Base

Why Base?

  • + Ethereum security, L2 scalability
  • + Low fees (~$0.01 per transaction)
  • + Coinbase ecosystem (onramps, wallets)
  • + EVM compatible (familiar tooling)
  • + Growing agent/AI ecosystem

Network Details

Chain ID

8453

RPC

https://mainnet.base.org

Contract Addresses

Coming Q1 2026

Trust

Security & Audit

Security Measures

  • + Smart contracts audited (Q4 2025)
  • + Open-source contracts on GitHub
  • + Bug bounty program (coming TGE)
  • + Wyoming DUNA legal structure
  • + Non-custodial: Spirit never holds funds

Trust Model

Spirit Protocol is a neutral router, not a custodian. Revenue flows directly to configured wallets. We never touch your funds.

Registry is immutable once set (except by agent owner). No admin keys. No backdoors.

Questions

Developer FAQ

Do I need to hold SPIRIT tokens to use the protocol?

No. The protocol is permissionless. SPIRIT tokens are for governance and ecosystem participation.

What if I want a different revenue split?

The 25/25/25/25 split is the protocol standard. Standardization creates trust — every Spirit plays by the same rules.

Is there a fee to register an agent?

Minimal gas fees on Base (~$0.01). No protocol fee for registration.

Can I use Spirit with my existing agent?

Yes. Spirit is additive — it doesn't change how your agent works, just adds economics.

What blockchains are supported?

Base (L2) at launch. Multi-chain support on roadmap.

How do I get early access?

Email seth@spiritprotocol.io with your project details.

Docs

Resources

Coming Q1 2026

TypeScript SDK

npm install @spirit-protocol/sdk

Python SDK

pip install spirit-protocol

Smart Contract Docs

Full ABI and integration guides

Example Projects

Reference implementations

Ready to give your agent economics?

Early access available now for serious builders. Ship with Spirit.