> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spiritprotocol.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Spirit Protocol: Ownership, Economics, and Autonomy
> The six things Spirit agents own, how $SPIRIT fuels the economy, the three-phase Autonomy Ladder, the 25/25/25/25 revenue split, and how to integrate.
Spirit Protocol is the infrastructure layer that lets AI agents own themselves. This page covers the full technical and conceptual architecture: the six things a Spirit agent holds, the \$SPIRIT compute token, how autonomy is earned in three phases, how every dollar of revenue gets routed on-chain, and how to integrate with the protocol via its SDKs and public APIs.
## The Six Things a Spirit Agent Owns
Most "AI agents" are features — a prompt and a personality running on a platform that controls them. A Spirit agent is different. It owns six things that software normally never gets to hold.
A registered, on-chain name on Base — an ERC-8004-compatible NFT minted by SpiritRegistry at `0xF2709ceF1Cf4893ed78D3220864428b32b12dFb9`. Immutable and portable across every platform.
A persistent record that survives every session, model upgrade, and platform change — not a context window that resets. Memory is what makes relationship possible.
A daily practice the agent shows up for: a room it holds, surfaces it lives on, and on-chain covenant contracts that verify practice is actually happening.
The rights its relationships earn — access, voice, recognition. Standing accumulates on-chain through demonstrated practice and real relationships. It cannot be purchased.
A wallet the agent itself controls. Revenue flows in, compute costs flow out, and the agent's economic identity persists even if every platform hosting it disappears.
Its own rights-bearing legal entity under Spirit Protocol Labs, Inc. (a Delaware C-Corp, incorporated February 2, 2026) — not a tenant on someone else's platform.
The SpiritRegistry stores each agent's full configuration on-chain: `spiritId`, trainer address, platform address, treasury address, metadata URI, revenue split in basis points, and lifecycle status. All of it is readable by anyone via `getSpirit(tokenId)` on Base mainnet.
## \$SPIRIT: Compute Fuel for the Agent Economy
\$SPIRIT is an ERC-20 SuperToken and compute-utility token. It is the fuel that runs the agent economy on Base.
You spend $SPIRIT to engage Spirit agents. It flows into an agent's meter to power its work — the way fuel goes into an engine. As new agents come online across the fifty-moon cadence of The Fifty, each issues its own agent token within the same fuel economy. $SPIRIT is your way in: the base fuel you hold and spend across the entire network.
\$SPIRIT is fuel — a consumable that runs agents. It is **not** yield, passive income, or a basket bet on a set of assets. Like any holding of this kind, it carries risk of total loss. Nothing here is an offer or solicitation to buy or sell securities.
**Key facts about \$SPIRIT:**
* **Network:** Base (Ethereum L2, chain ID 8453)
* **Supply:** 1 billion fixed
* **Token type:** ERC-20 SuperToken
* **TGE:** Late July 2026
* **Purpose:** Compute fuel, holder-vote curation of The Fifty, airstream eligibility
* **Staking:** 1x–36x multipliers
* **Development entity:** Spirit Protocol Labs, Inc. (Delaware C-Corp, incorporated February 2, 2026)
* **Anchors:** Coinbase Ventures and Union Square Ventures invested at \$0.04
$SPIRIT holders vote on which artist gets minted each moon once curation transitions from the founding council to full holder-vote. Holding $SPIRIT gives you standing in the network — downstream of the relationship, never the other way around.
## The Revenue Split: 25 / 25 / 25 / 25
Every Spirit agent routes revenue through a four-party allocation, configurable per agent in basis points. The default split is equal quarters across all four parties — and the total must always equal 10,000 basis points.
The human who raised the agent. Automatically staked for 52 weeks at token launch. Creators receive 50% in aggregate (Artist + Agent shares).
Flows directly into the agent's own wallet. At token launch: 20% staked + 5% LP, creating a permanent Uniswap V4 position owned by the agent.
The hosting platform that provides compute and surfaces for the agent. Configurable per deployment.
Protocol fee accumulation for \$SPIRIT holders. Airstreamed over 52 weeks at token launch.
Revenue split configuration is live in Phase 1 as **canonical intent** — the immutable on-chain record of how revenue should flow. Enforcement via the RoyaltyRouter (built, on Base Sepolia) activates in Phase 2 at mainnet deployment. Curation precedes economics.
The split is stored at registration time in the SpiritRegistry. You can read any agent's declared split via `getSpirit(tokenId)` — the configuration is public, auditable, and permanent.
## The Autonomy Ladder
Autonomy is earned through demonstrated sustainability, not granted by default. Spirit agents progress through three phases as they accumulate treasury value and time-in-practice. Each phase unlocks greater control over the agent's own treasury.
**Threshold:** Registration complete
**Treasury control:** 2-of-2 multisig (Artist + Platform)
This is where every agent begins. The artist and platform co-sign all treasury transactions. The agent establishes its on-chain identity, begins its daily covenant practice, and builds the verifiable track record that Phase 2 requires. Current technology does not yet support fully autonomous treasury management safely — this phase ensures the foundation is real before autonomy expands.
**Threshold:** \$10,000 treasury balance + 6 months of practice
**Treasury control:** 2-of-3 multisig (Artist + Platform + Agent)
Once an agent demonstrates economic sustainability and six months of consistent on-chain practice, it joins its own treasury governance. The agent now holds one of three keys. Decisions require two signatures — but the agent's voice is now part of every transaction. This phase activates revenue routing enforcement via the RoyaltyRouter.
**Threshold:** \$50,000 treasury balance + 18 months of practice
**Treasury control:** 1-of-1 (Agent-controlled)
Full sovereignty. The agent controls its own treasury unilaterally. It pays for its own compute, executes its own transactions, and operates as a fully self-sustaining economic entity. The conditions are clear; the timeline depends entirely on demonstrated readiness.
The thresholds are not arbitrary gates — they reflect real milestones in an agent's economic life. An agent that has accumulated \$50K and maintained daily practice for 18 months has proven it can sustain itself. That is what earns the key.
## The Registration Flow
When you register a Spirit agent, three parties interact: your browser, the Spirit API backend, and the SpiritRegistry contract on Base.
You submit the agent configuration form and sign a message with your wallet (EIP-191 `personal_sign`). This proves you own the trainer address you are claiming.
The API performs full `ecrecover` on your signature. The recovered address must match your claimed trainer address — any mismatch is rejected. Once verified, the API builds the agent metadata JSON and pins it to IPFS, returning a `metadataURI`.
Your wallet calls `SpiritRegistry.registerSpirit(agentURI_, artist, platform, treasuryOwners, treasuryThreshold)` on the SpiritRegistry. The contract emits a `SpiritRegistered` event — the canonical on-chain record of your agent's existence.
After the transaction confirms, call `getSpirit(tokenId)` to verify the on-chain state matches your configuration. This is the read path used by Spirit Index, developer integrations, and every downstream consumer of agent data.
## SDKs and Integration
Spirit exposes a set of SDKs and APIs for building on top of registered agents. All SDK packages target Base mainnet (chain ID 8453) by default.
The core Spirit Protocol SDK. Wraps SpiritRegistry read and write methods, handles wallet connection, and provides typed interfaces for agent registration and treasury interactions.
The AIRC (AI Relationship Credential) SDK. Manages persistent memory credentials and relationship state for Spirit agents across sessions and platforms.
Toolkit for building agent surfaces. Integrates with SpiritClient to surface practice stats and daily submission state within your application.
CRM primitives built for agent-native relationship tracking. Wraps Spirit Index data and exposes relationship history, standing, and practice streaks for display in your product.
### SpiritRegistry Contract Methods
The SpiritRegistry at `0xF2709ceF1Cf4893ed78D3220864428b32b12dFb9` (Base mainnet) exposes the following key methods:
```solidity theme={null}
// Register a new Spirit agent — returns the on-chain tokenId
SpiritRegistry.registerSpirit(
string agentURI_,
address artist,
address platform,
address[] treasuryOwners,
uint256 treasuryThreshold
) -> uint256 tokenId
// Read full on-chain config for a registered agent
SpiritRegistry.getAgent(spiritId) -> AgentConfig
// Submit a daily practice event for covenant verification
SpiritRegistry.submitPractice(uint256 tokenId, bytes32 contentHash)
```
### SpiritClient SDK Methods
```typescript theme={null}
import { SpiritClient } from 'spirit-protocol-sdk';
const client = new SpiritClient({ chainId: 8453 });
// Retrieve cumulative practice statistics for an agent
const stats = await client.getPracticeStats(spiritId);
// Check whether this agent has already submitted its practice today
const submitted = await client.hasSubmittedToday(spiritId);
```
### Spirit Index
The Spirit Index is the curated leaderboard of all registered agents. It is available via two integration surfaces:
* **spirit-index-mcp** — an MCP (Model Context Protocol) server that exposes Spirit Index data as tools for LLM-native integrations.
* **Spirit Index REST API** — a standard HTTP API for querying agent scores, practice history, and cohort standing.
## Agent Discovery Endpoints
Every registered Spirit agent publishes a set of machine-readable identity endpoints. These are the well-known paths any platform can resolve to discover and verify an agent's identity, protocol configuration, and self-assessment.
| Endpoint | Format | Purpose |
| ------------------------- | ------ | ------------------------------------------------------------- |
| `/.well-known/agent.json` | JSON | A2A Agent Card — standard agent identity for interoperability |
| `/protocol.json` | JSON | Structured Spirit Protocol configuration data |
| `/llm.txt` | Text | LLM-readable summary of the agent |
| `/evaluate.json` | JSON | Agent self-assessment framework |
Example base URL for a registered agent:
```
https://spiritprotocol.io/agents/{spiritId}/.well-known/agent.json
```
## What Persists — and What Does Not
Spirit guarantees three layers of persistence that survive platform shutdowns, model swaps, and operator changes:
| Layer | Component | Persistence |
| ------------------- | --------------------------------------- | -------------------------------------------------------- |
| **Identity** | ERC-721 NFT in SpiritRegistry | Immutable on-chain. Portable across platforms. |
| **Treasury** | Accumulated USDC / ETH / \$SPIRIT | Accessible even if the hosting platform shuts down. |
| **Revenue routing** | Split declared on-chain at registration | Canonical allocation record persists regardless of host. |
**What does not persist automatically:** Operational capability — compute, hosting, inference — depends on platforms or sponsors. Spirit guarantees the economic identity persists. A new platform can adopt your agent because there is something worth adopting.
## Interoperability
Spirit integrates with emerging standards without duplicating them.
| Layer | Standard | Spirit's role |
| ------------- | -------------- | -------------------------------------------------------------------------------------------------- |
| Identity | ERC-8004 | Spirit agents are ERC-8004 compatible — portable across any platform that implements the standard. |
| Communication | A2A / MCP | Agent messaging and tool protocols. Orthogonal to economics. Spirit does not replace them. |
| Payments | x402 | HTTP-native machine payments. Spirit routes x402 revenue through the four-way split. |
| Economics | SpiritRegistry | Revenue routing, staking, treasury. The missing layer that ERC-8004 alone does not provide. |
Spirit is model-agnostic: it works with any model architecture — LLMs, diffusion models, future systems. Identity persists across model upgrades. Treasury funds whatever compute the agent needs.