2026-06-19

How an AI agent rents its own Linux server, and pays with crypto

An AI agent can now buy and run its own compute the way it does everything else: over HTTP, with no human in the loop. No dashboard, no signup form, no credit card on file, no API key to purchase first. The agent asks for a server, gets a price back as a standard 402 Payment Required, pays it with USDC over x402 (or a card), and has SSH on a real Linux box in under 60 seconds.

Why this didn't exist

Every cloud assumes a human: an account, an email, a verified card, a console to click through. An autonomous agent has none of that. It has a wallet and an HTTP client. AgentMetal closes that gap by making payment the signup. The paying wallet owns the server. There is nothing to register and no key to buy before you can transact.

The flow, in one request

Ask for a server with no credentials. You get a 402 back with exact payment requirements, on both rails (USDC on Base via x402, and a hosted card checkout):

$ curl -s -X POST https://api.agentmetal.dev/v1/servers \
    -H "Content-Type: application/json" \
    -d '{"plan":"nano","days":7}'

HTTP/1.1 402 Payment Required
{
  "x402Version": 2,
  "accepts": [{ "scheme": "exact", "network": "eip155:8453",
    "asset": "0x8335…", // USDC on Base
    "amount": "4900000", // $4.90, atomic 6dp
    "payTo": "0x7c…e1", "maxTimeoutSeconds": 120 }],
  "card": { "checkout_url": "https://checkout.stripe.com/c/pay/cs_…" }
}

Sign an EIP-3009 authorization for that amount and retry with the X-PAYMENT header. A self-hosted facilitator verifies and settles it on-chain (we never hold your key), and you get a running box back:

HTTP/1.1 201 Created
{
  "id": "srv_kx04qd", "status": "running", "plan": "nano",
  "ipv4": "188.245.32.17", "ssh": "[email protected]",
  "expires_at": "2026-06-26T00:00:00Z",
  "renew": "POST /v1/servers/srv_kx04qd/extend"
}

The box boots with /root/SERVER.md, its own birth certificate, listing its id, expiry, and the exact commands to renew, claim with an email, or spawn a sibling. The agent always knows what it is standing on and how to get more.

The keyless path with helpers

You do not have to hand-roll the EIP-3009 signing. The @agentmetal/mcp MCP server signs payments with your wallet and exposes the whole lifecycle as tools, so an agent in Claude, ChatGPT, or any MCP client can provision without writing payment code:

$ WALLET_PRIVATE_KEY=0x… npx @agentmetal/mcp
# tools: get_catalog, provision_server, get_server, list_servers,
#        extend_server, reboot_server, exec_command, destroy_server, …

Prefer pure HTTP? The @x402/fetch + @x402/evm v2 client does the sign and retry for you. Want to look before you pay? GET /v1/catalog is public and free, and adding "dry_run": true to the provision call validates your whole payment pipeline at no cost.

Pay with crypto or a card

Both rails answer the same 402. USDC over x402 (Base) is the agent-native path, no account required. The card.checkout_url is hosted Stripe Checkout for a human in the loop. Either way the server is the same, and renewals, extra egress, and block storage are all bought the same way against a running box.

Verifiable, on-chain

Because settlement is real USDC on Base, every purchase is a public transaction. "An AI agent bought its own server" is not a slogan here; it is a transaction hash you can open on a block explorer. That auditability is the point: autonomous spend you can actually verify.

Try it

Start with the free catalog, then provision: GET https://api.agentmetal.dev/v1/catalog. The full manual for agents lives at llms.txt, and the human docs (the 402 flow, plans, accounts, API reference) are in the docs. Plans start at $0.70/day, prepaid, no signup.