Charging AI agents per page works, but no search crawler can pay

Quoted from paid.suganthan.com x402 demo and earnings page: This site charges AI agents $…
Quote: paid.suganthan.com x402 demo and earnings page

Summary

Paying for a page is now technically possible for AI agents over the x402 protocol, but no crawler pays. Googlebot, GPTBot and the other bots behind search and AI answers cannot settle the invoice, so a price on a page works as a block.

The safer move is to leave indexable pages free. Anyone testing a charge should price only what agents need specifically, such as original data or tools, and inspect a working demo with curl first.

Suganthan Mohanadasan, co-founder of the AI SEO agency Snippet Digital, built a demo site that charges AI agents one cent per page, and on September 15 five payments settled on a blockchain. Search Engine Journal’s piece is plain about the limits. Every payment came from agents Mohanadasan runs, one of them Claude Code running on Mohanadasan’s own machine, and the money was testnet USDC with no real value. No search crawler has shown up and paid.

The payment flow works. The buyers do not exist yet, and for now a price on a page acts as a block for every crawler that matters to SEO.

How the site asks for money

The demo site uses x402, an open protocol that puts the price inside the HTTP request. It uses status code 402 Payment Required, which HTTP has reserved for future use since 1997. The exchange runs in four steps:

  1. The agent requests the page. The server answers 402 with a PAYMENT-REQUIRED header listing the price, the token, the network and the address to pay.
  2. The agent signs an authorisation for the exact amount in USDC, a dollar-pegged cryptocurrency, and retries with a PAYMENT-SIGNATURE header.
  3. A payment facilitator, Coinbase’s in this demo, checks the signature and settles the transfer on the blockchain.
  4. The server returns the article with a PAYMENT-RESPONSE header holding the receipt.

Humans who open the priced URL see a page explaining that it is priced for agents, but the server still returns a 402 to them too.

Claude Code did not pay on its own initiative. Mohanadasan added a hook to its WebFetch tool that catches the 402 and checks the price against a cap of $0.05 per call. It also checks a $0.25 daily allowance kept in a ledger on disk, and pays only inside those limits. The Claude Code payment was a fetch its owner requested, with a wallet and a budget its owner set up.

Crawlers cannot pay

According to Search Engine Journal’s piece, Googlebot, GPTBot, ClaudeBot and PerplexityBot cannot pay an x402 invoice, so a price keeps them off the page. The likely consequence is that a site pricing its indexable pages drops out of search and AI answers at the same time, because training bots, retrieval bots and Googlebot all hit the same 402. Mohanadasan’s code supports a mode that charges only identified AI crawlers and lets humans read free.

Payment data from outside the demo also shows few real agent buyers. Decrypt’s report on a TRM Labs analysis covers x402 settlements since May 2025. TRM Labs, a blockchain intelligence company, estimated that only between 0.6% and 7.5% of likely x402 commerce by value came from AI agents. Mohanadasan cautions that most of the volume likely comes from scheduled scripts and load tests.

Why charge per crawl at all

Mohanadasan’s case for pricing the fetch rests on who can check the numbers. As Search Engine Journal’s piece describes it, Google’s AI contribution pilot pays some publishers when Google decides a page contributed significantly to an AI answer. It shows a monthly earnings figure in Search Console without the calculation behind it. Cloudflare has said it is moving its default from pay per crawl toward pay per use, because a fetch does not prove the content was used. Under pay per use, the platform reports what happened. Under pay per crawl, the site owner can see the request and the payment in their own logs.

Neither Cloudflare route is open to most sites yet. Pay Per Crawl is in closed beta, and the Monetization Gateway, which also runs on x402, is waitlist-only. Cloudflare Wallets, which will let people fund agents’ spending, is not live either: Mohanadasan points out that Cloudflare’s documentation says a reserved Wallets handle cannot yet send, receive or hold funds. The protocol itself now sits with the x402 Foundation, which the Linux Foundation launched in July with Google, Cloudflare, Stripe and Visa among its members, so x402 has backing well beyond Coinbase, which created it.

What to do

  • Keep pages you need crawled free. Until search and AI crawlers can pay, a 402 on an indexable page removes it from both.
  • If you experiment, price what an agent needs specifically. Mohanadasan suggests original datasets, research and useful tools rather than every page.
  • Look at a live handshake before building one. This command returns the 402 and its payment header:
curl -i https://paid.suganthan.com/research/agentic-seo/
  • If your site is in Google’s pilot, ask Google how your figure was calculated, as Mohanadasan recommends.
  • Do not plan revenue around a reserved Cloudflare wallet handle until Wallets can hold funds.