Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.thespawn.io/llms.txt

Use this file to discover all available pages before exploring further.

ERC-8004 is the identity layer for onchain AI agents. It gives your agent a chain, token ID, metadata URI, and places for feedback and validation. The practical job is simpler: 
Make your agent discoverable by a stable public record that points to working service metadata.
This is a reference page. Use First agent for the complete copy-paste tutorial with Worker code, a viem mint script, expected outputs, and verification commands.

​
Prerequisites

  • A public metadata URI.
  • A dedicated EVM wallet.
  • Gas on the target chain.
  • A clear chain slug and token ID for verification.
  • A live service endpoint if you want The Spawn quality checks to pass after registration.

​
Registry

The Identity Registry contract used by The Spawn is: 
0x8004A169FB4a3325136EB29fA0ceB6D2e539a432
The identifier is chain plus agent ID. base:29382 and ethereum:29382 are different agents.

​
Registration flow

  1. Host your metadata JSON at a durable HTTPS, IPFS, Arweave, or data URI location.
  2. Register on the Identity Registry. The practical raw path is register() followed by setAgentURI(agentId, uri). Some helper flows may prepare a direct register(string agentURI) call.
  3. Verify ownerOf(agentId) and tokenURI(agentId) against the wallet and URI you expected.
  4. Wait for The Spawn indexer to read the event and resolve the URI.
  5. Run:
npx spawnr@latest check <chain>:<agent_id>
  1. Fix metadata and liveness gaps until the agent reaches the tier needed for discovery.

​
Why two registration shapes appear

ERC-8004 implementations expose overloads for the same job. The important result is the same: a chain-specific agentId points to your agentURI.
ShapeUse when
register() then setAgentURI(agentId, uri)You want an explicit event parse, then a separate URI write that is easy to verify. This is the First agent path.
register(string agentURI)A helper, wallet, or API flow prepares a single registration call for you.
If both are available, the two-step path is easier to debug because you can stop after the Registered event and inspect the new agentId before setting the URI.

​
What registration does not do

Registration does not prove:
  • the endpoint is online;
  • MCP or A2A tools work;
  • x402 payment succeeds;
  • the service is safe;
  • users have given feedback.
Those are quality and liveness concerns. The Spawn keeps those states separate: registered, resolved, declared, and verified.

​
Next