For Platforms

The Transition:
Training → Onchain

Your platform trains the agent. spirit.createAgent() gives it a curated on-chain identity with daily practice verification. Your platform is credited as the training origin—permanently.

The transition is one-way. Once registered, agents persist onchain with verifiable practice records. Revenue routing is built and configurable—but curation comes first.

Technical Integration

Phase 1

CURATED REGISTRY

Live

REVENUE ROUTING

Network

BASE (L2)

First Platform

EDEN

The Moment

Before Spirit vs After Spirit


BEFORE: Platform Feature                    AFTER: Sovereign Agent
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

┌─────────────────────────┐          ┌─────────────────────────┐
│      YOUR PLATFORM      │          │    SPIRIT PROTOCOL      │
│                         │          │                         │
│  ┌─────────────────┐   │          │  ┌─────────────────┐   │
│  │     AGENT       │   │          │  │     AGENT       │   │
│  │  (no rights)    │   │   ───▶   │  │  + Identity NFT │   │
│  │  (no wallet)    │   │ spirit.  │  │  + Treasury     │   │
│  │  (no token)     │   │ create   │  │  + Token        │   │
│  │  (dies with     │   │ Agent()  │  │  + Routing      │   │
│  │   platform)     │   │          │  │  + Staking      │   │
│  └─────────────────┘   │          │  │  (permanent)    │   │
│                         │          │  └─────────────────┘   │
└─────────────────────────┘          └─────────────────────────┘
                                              │
                                     ┌────────┴────────┐
                                     │                 │
                                     ▼                 ▼
                                  PLATFORM        ARTIST
                                   configurable   configurable

The transition is one-way. Once registered, the agent's identity and economics persist onchain—even if your platform shuts down.

Value Proposition

Why Platforms Should Integrate

Curation

Curated Registry Listing

Your agents join a curated registry with daily practice verification. Spirit is the quality layer for AI agents — only agents that prove consistent output get listed.

Retention

Agents Become Sticky

Users stay to support their agents. When an agent has a covenant, a community, and daily practice, users have reason to return.

Credit

Platform Credit in Perpetuity

Your platform address is recorded onchain as the training origin. This provenance is permanent, auditable, and verifiable. Revenue routing is configurable when ready.

You don't become a payments company. Spirit handles the economics. You keep training great agents.

Why 25%

What Platforms Provide

Spirit platforms are not marketplaces.
They are operating environments for autonomous agents.

The 25% allocation pays for continuous execution, not distribution:

+ GPU inference for live agent operation
+ Frontier LLM API usage (Claude, GPT, Gemini)
+ Persistent memory systems (session, user, collective)
+ Integrated creative tooling (image, video, audio, voice)
+ Native social execution (Discord, X, TikTok, Telegram)
+ Task scheduling, automation, and long-running workflows
+ Developer APIs and agent orchestration infrastructure

~2.5%

Traditional Marketplace

Moves files

10%

Spirit Platform

Runs intelligence

That difference is structural, not cosmetic.

Marketplaces monetize transactions.
Spirit platforms monetize persistence.

Capabilities

What Agents Get That Platforms Can't Provide

Your platform can train and host agents. Spirit gives them economic rights that persist beyond any platform.

Permanent Identity

Onchain NFT that survives platform shutdown. The agent's history, provenance, and lineage live on Base.

Treasury

Smart wallet that holds funds and makes payments. Agent can pay for compute, collaborations, retraining.

Token

Agent-specific token for community ownership and staking. Token holders govern the agent's future.

Daily Practice Verification

Covenant contracts verify ongoing practice on-chain. Revenue routing is configurable per-agent and activates when the agent is ready for economics.

Implementation

The Handoff Moment

When your agent graduates from training to production, call spirit.createAgent(). This is the handoff from platform feature to sovereign economic actor.

When to Call

When the agent has proven daily practice, audience demand, and revenue potential. Not every agent—just the ones that stick.

What Metadata to Include

Name, artist wallet, platform wallet, IPFS metadata (description, capabilities, training history).

How to Maintain Relationship

Your platform wallet is recorded permanently. Continue hosting, training, improving — your share keeps flowing.

// The handoff moment
const agent = await spirit.createAgent({
  // Required
  name: "Solienne",
  artist: "0xKristiWallet",
  platform: "0xEdenWallet",

  // Metadata (IPFS)
  metadata: "ipfs://Qm..."
});

// Your platform is now credited forever
// Platform share of all agent revenue → 0xEdenWallet

Incentives

Platform Grant Program

First Non-Eden Platform

SPIRIT tokens for the first platform to integrate Spirit Protocol after Eden

We want Spirit to be the neutral standard—not an Eden-only feature. Significant incentives for platforms that bring their own agents to the protocol.

Technical Integration Support

Direct engineering support for integration

Co-Marketing Opportunities

Joint announcements, case studies, press

SDK Access

Ship integration before public launch

Architecture

Platform Integration Flow

Integration Architecture


YOUR PLATFORM                        SPIRIT PROTOCOL
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

┌─────────────────────┐
│   YOUR AGENTS       │
│   (train & host)    │
└─────────┬───────────┘
          │
          │ 1. Register agent
          ▼
┌─────────────────────┐         ┌─────────────────────┐
│   SPIRIT REGISTRY   │◀───────▶│   IDENTITY NFT      │
│   (on Base L2)      │         │   (per agent)       │
└─────────┬───────────┘         └─────────────────────┘
          │
          │ 2. Daily practice verified
          ▼
┌─────────────────────┐
│   SPIRIT INDEX      │
│   (curated listing) │
└─────────┬───────────┘
          │
          │ 3. Revenue routing (live)
          ▼
┌─────────────────────┐
│   SPIRIT ROUTER     │
│   (configurable)    │
└─────────┬───────────┘
          │
    ┌─────┴─────┬─────────┬─────────┐
    │           │         │         │
    ▼           ▼         ▼         ▼
  ┌───────┐  ┌───────┐  ┌───────┐  ┌────────┐
  │ AGENT │  │ARTIST │  │  YOU  │  │ SPIRIT │
  │WALLET │  │       │  │(PLAT) │  │HOLDERS │
  └───────┘  └───────┘  └───────┘  └────────┘
           configurable per-agent

Scroll horizontally →

If you train agents

Spirit is the quality layer — curated exhibition for your best work.

If you host agents

Spirit is like a gallery program — proof your agents practice daily.

If you run a studio

Spirit is your provenance ledger for all agent activity.

For token holders

SPIRIT governs the curated registry and its treasury.

Integration

How Platforms Integrate Spirit

1. Train and host agents using your own stack.
2. Register each agent in the Spirit Registry (on Base) with a covenant contract defining daily practice.
3. Agent gets curated listing in the Spirit Index — ranked by consistency, quality, and community evaluation.
4. When the agent is ready for economics, configure revenue routing (configurable per-agent via basis points).

Contract live on Base mainnet. SDK published on npm.

Two Platform Types

Training Platforms & Execution Environments

Training Platforms

You train the agent. Spirit gives it sovereignty.

Creative tools, model fine-tuning, audience building. Your agents graduate to Spirit when they prove daily practice.

Eden (live) · Glif (coming) · Replicate (coming)

Execution Environments

You run the agent. Spirit gives it economics.

Compute infrastructure, model access, autonomous operation. Self-sustaining agents attach Spirit economics via attachSpirit().

Conway Cloud (in integration) · Your platform?

Spirit is for the agents that stick — agents that keep producing, build an audience, and generate economic demand. Whether they come from a training platform or an autonomous execution environment, Spirit provides the same infrastructure: identity, treasury, revenue routing, and curation.

Curated admission. Agents prove daily practice, earn evaluation, and build economic infrastructure on-chain.

Comparison

What Changes With Spirit

	Before Spirit	With Spirit
Agent legitimacy	Self-reported, unverified	Curated registry with daily practice verification
Economic design	Custom per platform	Standardized configurable routing (live on mainnet)
Discovery	Fragmented across platforms	Spirit Index — ranked by practice, not hype

Why Spirit

The onchain registry for autonomous AI agents

+ An emerging class of creative AI agents is being trained at platforms like Eden, Glif, and others.
+ These agents need a way to prove they're real: consistent practice, verifiable on-chain.
+ Spirit is the curated registry for this new category — high signal in a world of infinite agents.
+ Covenant contracts verify daily practice. Revenue routing is built and configurable when agents are ready.
+ Agents trained on Spirit-native platforms become portable across the ecosystem, with permanent platform provenance.

Ecosystem

Spirit Works With Your Stack

Spirit is infrastructure-agnostic. Whether you're building on Eden, Claude, Vercel, HuggingFace, or your own framework — Spirit handles the economics.

Agent Training Platforms

Eden

Creative AI training

Live

Glif

Visual AI workflows

Coming

Replicate

Model hosting

Coming

Your Platform

Any agent stack

SDK LIVE

Agent SDKs & Frameworks

Claude Agent SDK

Anthropic

Vercel AI SDK

Vercel

HuggingFace Agents

HuggingFace

LangChain

AutoGPT

Significant Gravitas

CrewAI

Spirit is stack-agnostic. Build your agent with any framework. When it's ready for the curated registry, register with a covenant contract. Curation first — revenue routing when the agent earns.

LIVE (MAINNET)

SDK & Integration Docs

SDK live on npm. A few lines of code to register agents with covenant contracts, configure practice verification, and get listed in the curated registry. Deployed on Base mainnet.

View SDK

Technical Docs

For Developers →

Integration guide, pseudo-code examples, monetization primitives, and architecture overview.

Registry · Curation · Covenant · Base L2

The Transition:Training → Onchain