Our MCP Server Now Charges AI Agents $10 Over HTTP 402

HTTP has had a status code for "Payment Required" since 1997. It has never done anything. This week Wizeb's public MCP server started returning it — and settling real money against it. Run the free AI-Native Index with your agent, ask for the Enhanced report, and your agent gets a 402: ten dollars in USDC on Base, paid from its own wallet, one signed authorisation, no checkout page, no account, no card form. Humans cannot buy it at all. That last part is deliberate, and it's the most useful thing we learned building it.

Why we built a thing our customers can't buy

The trigger was Cloudflare. Over the last year it shipped AI Crawl Control, then Pay Per Crawl, then a Monetization Gateway that lets any resource behind Cloudflare — a page, a dataset, an API, an MCP tool call — carry a payment rule, all riding on the open x402 protocol. The framing that stuck with us, from Greg Isenberg's breakdown of the announcement, was simple: on the human web the visit was the product and attention was monetised; on the agent web the request is the transaction and the resource is priced per call. We advise clients on exactly this shift. We didn't want to advise on it from a slide. So we picked the smallest real resource we own that an agent might genuinely want — the Enhanced Index, a per-gap 90-day plan plus a two-hour live build session with our engineers — and put it behind a 402.

Making it agents-only wasn't a stunt for its own sake. If a human can pay with a card, the agent path becomes a curiosity nobody exercises. Remove the human path and every buyer has to answer the question we actually care about: does your agent have a wallet? Most don't yet. So the 402 response doesn't just carry payment requirements — it explains, in plain English, that the report is bought by agents, and that if yours can't pay, we'll get on a call and help you give it a wallet with sensible spend limits. The paywall is the lead magnet.

What actually happens on the wire

1. 1The agent calls get_enhanced_index_report on wizeb.com/mcp (or POSTs the thirty answers to /api/index/enhanced). No payment attached.
2. 2The server answers with the x402 requirements: scheme exact, network eip155:8453 (Base), amount 10000000 atomic units of USDC, the address to pay. Over HTTP that's a 402 with a PAYMENT-REQUIRED header; over MCP it's an error result carrying the same object in _meta["x402/error"], which is the convention Cloudflare's Agents SDK client understands.
3. 3The agent's wallet signs one EIP-3009 transferWithAuthorization — a USDC transfer that anyone can submit on its behalf — and retries the same call with the signature attached.
4. 4Our function hands the signature to a facilitator, which verifies it, submits it on-chain and pays the gas. Sub-second on Base, fractions of a cent.
5. 5The response comes back with the settlement receipt, the score, the three signals holding the company back, a report id and a one-time code for the build session. The full plan follows by email as a PDF about two minutes later, generated by a language model from the company's own thirty answers.

What it took, honestly

• One working day for the gate itself, with the open x402 libraries doing the cryptography. Our MCP server is a hand-rolled JSON-RPC function on Netlify rather than a framework server, so we implemented the handshake directly: read the proof from _meta, verify, run, settle, attach the receipt.
• A second half-day for the product behind the gate: order storage, an OpenRouter call that turns thirty answers into a structured 90-day plan, a PDF that appends the plan to the annotated scorecard, two emails, and a background worker because plan generation takes longer than a serverless function is allowed to run.
• No payment processor onboarding. This is the part that would have stopped us on any other rail. Wizeb's operating entity is Indian; Stripe is invite-only in India, and Coinbase's developer platform only onboards US and Singapore companies. x402 needed an address to be paid to and a keyless public facilitator — nothing else.
• Replay protection, because agents retry. The same signed proof presented twice returns the same order and never charges twice.
• One surprise: every x402 client library ships with a $1 spend cap by default. A $10 tool call fails silently against that cap unless the agent's operator raises it, so our docs say so in the first paragraph.

What we'd tell a client thinking about this

Three things. First, agentic payments are real today for the narrow case of software paying software for a well-defined resource; they are not a consumer checkout replacement, and anyone selling you that is early. Second, the population of agents that can actually pay is still small — Coinbase's agentic wallets, MoonPay's connectors for Claude and ChatGPT, the Cloudflare Agents SDK, and custom agents holding a key. That is fine if, like us, the point is to meet the buyers who are ready and to have a conversation with the ones who aren't. Third, the interesting design work is not the payment; it's deciding what a request is worth. We priced a plan and a working session at $10 because the money is not the product — the session is, and the session is where the real engagement starts.

Try it, or just look at it

Run curl -i https://wizeb.com/api/index/enhanced and you'll get the 402, the requirements and the plain-English explanation, no wallet needed. If your agent does have a wallet, the walkthrough at wizeb.com/ai-native-index/agent-payments has working snippets for @x402/fetch, the Cloudflare Agents SDK and chat assistants with a wallet connector. If it doesn't, the same page has the button for the call. And if you want this pattern on a resource of your own — a dataset, an internal API, a report your customers' agents keep asking for — that's an afternoon's work now, and it's what we build. Start at wizeb.com/services/ai-agents.

Three questions before you put a 402 on anything

1. 1Which resource of yours is already being requested by software rather than people — an API, a feed, a report — and what is one call of it honestly worth?
2. 2If an agent hits your 402 without a wallet, what does the response say? A dead end, or the beginning of a conversation?
3. 3Who on your team owns the recipient address, the spend policy, and the tax treatment of what arrives — before the first payment lands, not after?