Suganthan Mohanadasan, an independent blogger, built a paywall that charges AI agents one cent per page using the x402 protocol, and on 15 September he watched Claude Code pay it mid task. The payment settled on a public blockchain with a visible transaction hash. Every payment so far has come from his own agents, not from a search crawler that found the toll on its own.
That caveat matters more than the demo itself. Mohanadasan is explicit that no independent crawler has discovered his priced page and paid to read it. The transactions also ran on testnet USDC, a test version of the stablecoin that carries no real monetary value. The infrastructure works. The market that would pay real money into it does not yet exist.
x402 revives an HTTP status code, 402 Payment Required, that has sat unused in the web’s specification since 1997. In Mohanadasan’s setup, an agent requests a page, gets a 402 response describing the price, signs off on moving precisely that sum in USDC, then sends the request again carrying a payment header. A facilitator (Coinbase’s, in this case) verifies the signature and settles the transaction, and the server releases the content with a receipt attached. No account, no API key, just a price and a signature.
He wired that flow into Claude Code through a hook that intercepts failed web fetches, checks the price against a spending cap he set in advance, pays if it clears the cap, and hands the retrieved page back to Claude as context. When the price exceeded his limit in testing, the script refused outright and printed a message telling the agent not to negotiate. That refusal, he argues, is the more interesting part of the demo: a budget only means something if the agent can be blocked from spending past it.
Mohanadasan’s experiment sits inside a wider shift already underway. Cloudflare announced Wallets for agent payments in early August and a Monetization Gateway on 1 July, both still gated behind waitlists as of mid-September. Google has separately begun paying some publishers, through an “AI contribution pilot” reported by Digiday and confirmed by Google, when a page is judged to have contributed to an AI-generated answer, though publishers in that program receive a total with no breakdown of how it was calculated. On 14 July the Linux Foundation stood up an x402 Foundation with about 40 members, including Visa, Mastercard, Google, AWS, Stripe and Cloudflare, which signals institutional buy in for the payment rail even as adoption by the crawlers that matter, GPTBot, ClaudeBot, PerplexityBot and Googlebot among them, has not happened.
Mohanadasan also flags a reporting caveat worth carrying into any claim about this market’s size: Decrypt reported on 13 September that the blockchain analytics firm TRM Labs went through 198.9 million settlements on x402 and concluded that most of that traffic probably came from somewhere other than AI agents, more likely scheduled scripts and same-party test traffic. A large transaction count proves the rail is being used. It does not prove agents are autonomously buying content from strangers’ websites.
The practical read for anyone running a content site: the tooling to charge agents per page now exists and works end to end, from AWS’s AgentCore payments (generally available since 18 August) to Cloudflare’s forthcoming gateway, but the buyers, the crawlers site owners actually want to charge, have not shown up yet. Blocking bots outright, negotiating a licensing deal, or waiting on Google’s opaque revenue share are still the only options that pay today. The decision worth making now, before pay per page becomes a checkbox in a dashboard, is which pages would be worth metering once an agent with a real wallet finally knocks.
Suganthan Mohanadasan detailed the experiment on his personal blog on 15 September 2026.
