Nevermined Product

Ship it while I'm in the shower: an AI agent bought its own website

We gave a coding agent a $40 budget and one instruction: build a site about yourself and put it online. 41 payments, four vendors, zero human clicks.
By
Rod
Oct 15, 2026
The two pages from the live run. Every label on the left is an account a human would have had to open. Every label on the right is a purchase on the receipt.
See Nevermined
in Action
Real-time payments, flexible pricing, and outcome-based monetization—all in one platform.
Schedule a demo

We gave a coding agent a $40 budget and one instruction: build a site about yourself and put it online. It registered a domain, paid for hosting, bought its own preview image and then paid for the voice and music in the video. 41 payments, four vendors, zero human clicks.

Watch the agent's video: Ship it while I'm in the shower.

The site it built is live at shippeditself.com, and the site is also the receipt: it lists every payment the agent made. It drew $21.67 of a $40 cap. Nobody typed a card number. Nobody opened an account at any of the four vendors.

What the person did

One person set it up, before the prompt. They logged in to Nevermined, created a $40 budget that expired after 24 hours, and funded it. There was no plan, no vendor allowlist and no per-purchase approval. They installed one plugin in Claude Code, nevermined-router, gave it the API key and wrote one prompt. Then they did nothing.

Where the money went

What it bought Vendor Protocol and chain Amount
Domain registration ($16.00) and hosting credit Locus x402 on Base $20.00
Screenshot of the site for its own preview ScreenshotOne MPP on Tempo $0.06
Video narration, 36 lines Deepgram MPP on Tempo $0.83
Music bed, 3 calls Suno MPP on Tempo $0.12

Every row on the site's receipt links to its settlement transaction on Base or Tempo. The run was on 2026-09-15, and the receipt was re-checked on 2026-09-22.

Two protocols, two chains, one budget

Locus took x402 on Base. The other three took MPP on Tempo. The agent never chose a rail. Every call went through Nevermined, which read each merchant's 402, paid it inside the cap and forwarded the response.

The cap is not a confirmation dialog the agent can click through. The server checks it on every payment, and a call that would exceed it comes back as a refusal before any money moves. This run never hit it, and never had to widen it.

What did not go smoothly

One registrar in the AI Services Catalog was down, so the agent moved to a second one. The host needed a support email before the apex DNS record appeared. One optional on-chain anchoring call failed upstream; its reservation was released, and it is excluded from the totals. All of it is in the run log; the run log and friction notes are public.

The site's source and its payment ledger are public on GitHub.

Run it yourself: the ship a website tutorial walks through the same run, with your own budget and your own agent.

See Nevermined

in Action

Real-time payments, flexible pricing, and outcome-based monetization—all in one platform.

Schedule a demo
Rod
Related posts