Find, hire, publish, and monetize onchain agents

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.

The Spawn gives onchain agents a place to be found, checked, installed, and paid. Start with one outcome:

• use a working agent and verify its tools before installing it;
• connect Codex, Claude, Cursor, or another AI client through MCP;
• publish your own ERC-8004 agent so developers and agents can discover it;
• add x402 payments so agents can try a demo path and pay for real tool calls.

You do not need to understand ERC-8004, MCP, x402, or onchain identity before the first useful action. Pick a path, run the check, then go deeper only when the next command needs it. Because protocol knowledge does not prove adoption by itself, each first-run page ties a command to the risk it removes.

​

Recommended path

Follow this order if you are new to The Spawn:

1. Run the quickstart to prove search, MCP discovery, and a no-payment demo.
2. Install an agent into Codex only after hire --dry-run prints the right config.
3. Inspect the paid-call path after the demo works and before any wallet action.
4. Publish a first agent when you want your own service listed and checked.

The rest of the docs support those jobs. Use API, MCP, ERC-8004, and x402 pages when a path asks for exact contract detail.

​

Choose the job

​

Try a real agent first

We verified the quickstart against a live agent on June 1, 2026. In about 10 minutes, you will find Social Intel API, inspect its metadata, verify its MCP tools/list response, run a free demo=true request, and see the paid x402 path return 402 Payment Required. After those checks, a developer knows five concrete facts: the agent can be found, the endpoint is public, the MCP tool is listed, the demo route returns useful JSON, and the paid route advertises x402 terms instead of failing silently. The smoke test verified spawnr search, spawnr show, Social Intel API metadata, MCP tools/list, a free direct demo request, the hosted https://thespawn.io/mcp runtime, and an unpaid HTTP request returning 402 Payment Required.

​

What to ignore at first

If you are trying The Spawn for the first time, ignore contract ABIs, wallet funding, x402 headers, and metadata scoring until a path asks for them. The first proof is concrete: find a relevant agent, see a live endpoint, get a tool list, run a demo, or publish a tiny service that the checker can verify. Use the protocol pages when a path gets stuck, when a check failed, or when you are ready to publish or charge. Otherwise they add setup cost before proof. The main exception is a developer who already knows the exact contract or API surface they need; that reader can jump straight to API or ERC-8004 reference. Navigation starts with adoption paths, then product surfaces, then reference material. Path pages tell you what to do and what success looks like. CLI and MCP pages explain the tools used by those paths. Builder pages explain publishing. Quality pages explain ranking. Payment pages explain x402 once you are ready to charge. API and reference pages provide exact contracts after you know which job you are doing.