Google started paying some publishers this month when their content feeds AI answers. The programme, called the AI contribution pilot, was reported by Digiday on 14 September and confirmed by Google. Publishers get a monthly earnings figure in Search Console. They do not get the formula behind it.

Separately, a developer named Suganthan Mohanadasan built a working pay-per-crawl system on his own site using the x402 protocol. On 15 September, five testnet payments settled on a blockchain, one of them triggered by Claude Code during a live task. The two approaches expose a fundamental question about how content owners get paid when AI agents read their work.

How Google's pilot handles publisher payments

Google pays when it determines a page contributed significantly to an answer while it was being generated in AI Overviews, AI Mode, or the Gemini app. A page linked after the fact does not qualify. Search Engine Land detailed the eligibility rules on 14 September.

According to Digiday, Google approached dozens of publishers, with smaller outfits showing more interest. One executive familiar with the programme called it a black box. Barry Schwartz at Search Engine Roundtable had found the help page back in April, but the feature's purpose was not clear at the time.

The core problem: publishers see a total, not the reasoning behind it. That opacity makes it hard to judge whether the compensation matches the value extracted.

The pay-per-crawl alternative

Suganthan's approach flips the model. Instead of waiting for a platform to decide what content is worth, the site sets a price before an agent reads it. Pay the cent, get the content. Refuse, and the server holds it back.

The implementation runs on Cloudflare Workers with about 300 lines of Hono code. It has been live since 8 August at paid.suganthan.com. Three routes exist: a free landing page explaining the demo, a priced article at /research/agentic-seo/ costing $0.01 per crawl, and a public /earnings/ page showing every transaction with timestamps, payer addresses, and settlement hashes.

The server enforces payment. This is not robots.txt, where compliance depends on a crawler choosing to follow the rules. An HTTP 402 response blocks access until payment clears.

What x402 actually does

HTTP has included status code 402 since 1997. It was reserved for future use. The x402 protocol, now operational under the Linux Foundation with 40 members including Visa, Mastercard, Google, AWS, Stripe, and Cloudflare, gives it a real function.

The exchange is four steps:

  • An agent requests a page. The server responds with 402 and a PAYMENT-REQUIRED header describing the price, token, and destination address.
  • The agent signs an authorization to transfer the exact amount in USDC and retries the request with a PAYMENT-SIGNATURE header.
  • A payment facilitator (Coinbase's at x402.org in this demo) verifies the signature and settles the transaction on-chain.
  • The server returns the content with a PAYMENT-RESPONSE header containing the settlement receipt.

The payment offer decoded from a live 402 response requests 10,000 units of USDC on Base Sepolia. USDC uses six decimal places, so 10,000 equals $0.01. A compatible client pays without creating an account or requesting an API key.

Notably, the buyer wallet held zero ETH. The facilitator covers gas fees. The agent only needs the USDC it is spending.

Watching Claude Code pay during a task

The most interesting part of the demo involved Claude Code hooks, which run scripts around tool calls. When Claude tried to fetch a priced page and encountered a 402, the hook decoded the payment offer, checked the price against a per-call spending cap, paid if authorized, and passed the content and receipt back as context.

The receipt from one session reads:

Paid $0.0100 for "https://paid.suganthan.com/research/agentic-seo/" via x402.
Settlement tx: 0x51b5eba4fb34ddff27052d89cb79ae3d748b379800a723a6f4f020c11e2871c9

The buyer script includes spending guardrails: a $0.05 maximum per call and a $0.25 daily allowance tracked in a local ledger. When the price exceeds the cap, the script refuses and exits without signing. The agent cannot override its own budget.

That boundary matters. An agent that pays any price a server quotes is not operating within a budget. It is draining a wallet.

Cloudflare's wallet infrastructure

During Agents Week on 4 August, Cloudflare announced Wallets and opened handle reservations. The system splits into Account Wallets for humans (funding, limits, allocation) and Virtual Wallets for agents (spending within permissions). The handle gives an account a recognizable identity.

As of mid-September, a reserved handle displays a name and a notification that Wallets is coming. It cannot send, receive, or hold funds yet. The Monetization Gateway, announced 1 July, remains on a waitlist.

AWS made AgentCore payments generally available on 18 August. Agents using it can encounter a 402 and pay through x402. Cloudflare's Agents SDK also includes a payment client. The infrastructure exists, but the crawlers most site owners care about, GPTBot, ClaudeBot, PerplexityBot, and Googlebot, do not yet arrive with wallets.

What this means for site owners

Requiring payment right now means blocking the crawlers that surface and cite your content without earning anything in return. The trade-off is real.

The more practical question is which pages to charge for. General explainers still earn value through citations and discovery. Original datasets, proprietary research, and functional tools are better candidates. An agent needs specific data from those resources to complete a task. A per-request fee fits that use case better than an advertising model built for human readers.

Google's pilot addresses value from the platform side. Pay-per-crawl addresses it from the publisher's side. The publisher controls the price and can independently verify every transaction. The platform decides what to pay, and the publisher sees only the final number.

TRM Labs examined 198.9 million x402 settlements, as Decrypt reported on 13 September. Most of the volume did not come from autonomous AI agents. Scheduled scripts, load tests, and same-party payments produce similar records. The payment infrastructure works. Whether agents are actually buying useful content from independent sites at scale remains an open question.

Suganthan's demo uses testnet tokens, so no real money has changed hands yet. The code supports the real Base network. The next step is a single live transaction. When an agent pays a real cent for a page, the settlement hash will tell the story.

Cloudflare's Monetization Gateway and wallet system will eventually make this a standard configuration. Having thought through what to charge and why, before that option appears in a dashboard, puts publishers in a stronger position than accepting whatever a platform decides their content contributed.