Google is paying several publishers whenever their satisfied helps create its AI answers.
Barry Schwartz covered it at Search Engine Roundtable on September 14, following Digiday’s report that morning. Google confirmed the program to Digiday. It’s called the AI contribution pilot.
Publishers who obtain the conditions get an earnings fig in Search Console all month. What they don’t get is a breakdown of how Google calculated it.
Google pays whenever it decides a leaf contributed considerably to an answer during it was being generated in AI Overviews, AI Mode, or the Gemini app. If the leaf lone gets connected following the answer has been written, it doesn’t qualify.
I’m not in the pilot. According to Digiday, Google has approached at smallest dozens of publishers, alongside smaller publishers showing additional involvement than the larger ones. One administrator acquainted alongside it described it as a dreary box. Barry had really found the assistance leaf rear in April, but it wasn’t apparent afterward what the characteristic did.
I’ve been evaluation a distinct method on my own location since August.
My leaf sets a cost before an delegate says it. If the delegate wants access, it pays.
On the dawn of September 15, five payments went through. Each one settled on a blockchain and has a community transaction hash. One came from Claude Code, operating on my device and using a wallet I’d set up for it.
To be clear, all the payments so far have arrive from my own agents. No hunt crawler is turning up and paying me. The payments additionally use testnet USDC, which method the tokens have no genuine monetary value.
But the fee procedure works. An delegate requests a page, checks the price, pays and receives the content. Cloudflare is construction products about that identical idea, and I wanted to comprehend how it plant before it becomes another environment in a dashboard.
What That Cloudflare Wallet Handle Is For
On August 4, during Agents Week, Cloudflare announced Wallets and opened grip reservations.
Claiming a grip is free. I doubtful plentifulness of group grabbed theirs the way we grab usernames: quickly, before person alternatively gets there, alongside a vague aim of study the particulars later.
If you did that, this is the benevolent of item those wallets are being built for.
Cloudflare’s scheme has two parts:
- Account Wallets pertain to people. You add funds, set spending limits, and allocate prosperity to your agents.
- Virtual Wallets are for the agents. They expend inside the permissions and limits you’ve set.
Your grip gives that document a recognizable identity.
As of September 15, though, reserving a grip gets you a leaf displaying the name and a notification whenever Wallets becomes available. Cloudflare’s documentation explicitly says a reserved grip can’t yet send, receive, or clasp funds.
The another part is the Monetization Gateway, which volition let sites accusation agents for admission to resources. Cloudflare announced it on July 1, and admission is motionless through the waitlist connected from that announcement.
So the products are announced, but you can’t yet use a reserved wallet grip to run this entire process.
My demo shows what that procedure looks akin today using x402. The location charges one cent per page; my delegate pays, and spending limits authority what it can buy. It’s the identical broad institution Cloudflare describes for Virtual Wallets.
Why Charge Crawlers At All?
The institution between hunt engines and websites used to be fairly straightforward. Search engines crawled your content, showed it in their results, and sent visitors back.
Publishers got traffic. Search engines got item helpful to display their users.
AI answers have changed that arrangement. An delegate can peruse your page, use the data in its response, and answer the person without sending them to your site.
I’ve spent months looking at what these systems really fetch. There’s plentifulness of crawling. The traffic coming rear frequently doesn’t indicate it.
Publishers have responded in distinct ways, partially depending on how much negotiating power they have.
Smaller sites frequently block AI crawlers. I comprehend why. If person is taking your satisfied and you’re getting small in return, blocking them is a sensible response. But it comes alongside a trade-off: restricting admission can additionally decrease your visibility in training datasets and AI answers.
Large publishers can negotiate licensing deals. News Corp, the Financial Times and Reddit all have agreements alongside AI companies. According to Press Gazette’s reporting on 4 September, People Inc.’s chief administrator told investors that blocking crawlers through Cloudflare had helped bring AI companies to the negotiating table.
Google’s aviator offers another approach: paying publishers according to the value their satisfied contributes to AI answers.
In that identical Press Gazette piece, Cloudflare stated it was moving its own default method from pay per crawl towards pay per use, alongside pilots involving Ceramic.ai and You.com. Its reasoning was that fetching a leaf doesn’t demonstrate the satisfied was really used.
I think that difference matters.
Using a leaf to answer a inquiry is a stronger sign of value than merely downloading it. But it’s additionally item the website owner can’t independently observe. Once my leaf has remaining my server, I can’t see whether it influenced an answer.
With pay per use, I’m relying on the phase to inform me what happened and what it was worth. With pay per crawl, I can inspect the petition and the fee myself.
Google’s eligibility rules create this particularly clear. As Barry Schwartz explains, contributing during answer generation can acquire a payment. Being connected afterwards doesn’t. The publishing company sees the total, without the calculation rearward it.
Each method leaves item unresolved.
Blocking earns nothing directly. Individual licensing agreements don’t measure to millions of small websites. Revenue-sharing arrangements depart the phase deciding how much to pay.
Putting a cost into the petition gives a location a norm way to market access. An delegate can obtain that cost and obtain the content, alongside a receipt for the transaction. There’s no need to negotiate a distinct business accord alongside all buyer.
That’s the pay-per-crawl example I wanted to test.
Cloudflare already has a merchandise called Pay Per Crawl, but it’s motionless in closed beta. On the paying side, bot operators need verification through Web Bot Auth, Stripe onboarding, and program approval.
My individual delegate can’t merely associate that program.
So I built a type using the open x402 protocol, which Cloudflare is additionally using for its upcoming Monetization Gateway. My demo makes genuine x402 payments independently of Cloudflare’s closed Pay Per Crawl programme.
How x402 Works
HTTP has included a position code called 402 Payment Required since 1997. The specification reserved it for forthcoming use.
Twenty-nine years later, x402 gives it a applicable purpose.
In my setup, the toggle has four steps:
- The delegate requests a page. The server responds alongside 402 Payment Required, including a PAYMENT-REQUIRED header that describes the cost and fee requirements.
- The delegate signs an authority to transfer the exact amount in USDC. It afterward retries the petition alongside a PAYMENT-SIGNATURE header.
- A fee coordinator verifies the signature and settles the transaction on the blockchain. My demo uses Coinbase’s coordinator at x402.org.
- The server returns the content, alongside alongside a PAYMENT-RESPONSE header containing the colony receipt.
Here’s the recommendation from my site, decoded from a live 402 reply this morning:
{ "x402Version": 2, "accepts": [{ "scheme": "exact", "network": "eip155:84532", "amount": "10000", "asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e", "payTo": "0xEdF2444D0259BBB8aC5094216D0148938F8308ff", "maxTimeoutSeconds": 300, "extra": { "name": "USDC", "version": "2" } }] } That recommendation asks for one cent in testnet USDC on Base Sepolia, paid to the burner wallet I’m using for the demo.
USDC uses six decimal places, so 10000 represents 0.01 USDC.
A compatible client can peruse those fee requirements and pay without creating an document alongside my location or asking me for an API key.
That’s a helpful difference from robots.txt. A regulation in robots.txt depends on a crawler choosing to regard it. Here, the server can withhold the protected satisfied until fee succeeds.
The buyer wallet additionally held zero ETH, yet all colony went through. The coordinator submitted the transactions and covered the blockchain transaction fees, normally called gas. I checked the balances twice.
For this setup, the delegate lone needed the testnet USDC it was spending.
There’s broader industry assistance rearward the protocol too. The x402 Foundation became operational under the Linux Foundation on 14 July, alongside 40 members, including Visa, Mastercard, Google, AWS, Stripe and Cloudflare.
That’s helpful context, but the genuine toggle is motionless those four steps.
What’s Running On My Site
The demo is at paid.suganthan.com.
It runs on a Cloudflare Worker, using approximately 300 lines of Hono code and the x402 middleware. It’s been operating since August 8, and the community earnings leaf records all paid crawl since then.
There are three routes:
- The landing page is liberated and explains the demo.
- /research/agentic-seo/ charges $0.01 per crawl.
- /earnings/ shows the operating total, timestamps, payor addresses, and transaction hashes.
Request the part alongside curl, and you’ll get this:
$ curl -i https://paid.suganthan.com/research/agentic-seo/ HTTP/2 402 payment-required: eyJ4NDAyVmVyc2lvbiI6MiwiZXJyb3Ii...
Open the identical URL in a browser, and you get a leaf explaining the charge. It motionless returns HTTP position 402, but a individual visitant gets item readable.
There’s additionally a preview button. That opens the part for liberated alongside a banner, so you can inspect the satisfied as fine as the fee screen.
I built another manner that isn’t enabled in the demo. Changing one changeable makes the Worker accusation lone requests that acknowledge themselves as known AI crawlers, including GPTBot, ClaudeBot, and PerplexityBot. Human visitors can browse for free.
I tested that manner using spoofed user-agent strings, and it behaved as expected.
Of course, those strings can be faked. Checking a person delegate is adequate to display the behaviour, but it doesn’t demonstrate who made the request. Cloudflare’s method uses cryptographic verification of crawler character to location that problem.
Giving The Agent A Budget
The buyer is a small Node script. Before it pays, it checks whether the petition fits its budget.
I gave it two limits:
- A maximum of $0.05 per call.
- A $0.25 regular allowance, recorded in a spending ledger on disk.
The manuscript decodes the fee recommendation and checks the two limits before authorizing anything.
If the petition is inside budget, it pays, retries the request, prints the colony details, and records the spend. If it exceeds either limit, it refuses.
Here’s a refusal alongside the per-call cap set below the page’s price:
[step 3] Spending guardrails [refused] Price $0.0100 exceeds the per call cap of $0.0010. This delegate does not negotiate. Raise MAX_PER_CALL to override.
That refusal is among the most helpful parts of the demo.
If an delegate pays all cost a server gives it, you haven’t really delegated a budget. You’ve stated it a way to bare a wallet.
The spending checks happen before signing. When the petition fails those checks, the manuscript exits alongside code 3 without creating a fee signature.
This follows the identical broad scheme Cloudflare describes for its wallets: a individual provides the finances and sets the limits, and an delegate spends inside them. My buyer manuscript demonstrates that behavior without being an genuine Cloudflare Virtual Wallet.
The prosperous run in the screenshot settled at 07:21 UTC. Two before payments went through at 06:10 and 06:11, alongside the second motionless inside the regular allowance.
All three appeared on the public earnings page inside seconds of confirmation.
The seller’s balance increased, the buyer’s balance decreased, and the amounts matched. The August transactions are motionless listed underneath them. I haven’t touched the fee code since those before payments.
Watching Claude Pay During A Task
This was the part I was most curious in.
Claude Code supports hooks: scripts that can run about tool calls. Cloudflare documents a form that watches WebFetch, and I connected that form to my wallet.
The procedure plant akin this:
- Claude tries to fetch a leaf and encounters a 402.
- The hook requests the fee recommendation itself.
- It checks the cost against the per-call spending cap.
- If the cost is allowed, it pays and retrieves the content.
- It passes the satisfied and receipt rear to Claude as additional context.
Claude can afterward continue alongside its task. I don’t have to halt what I’m doing and manually pay for the page.
That’s what happened in the meeting shown near the top of this article. The hook returned this receipt:
Paid $0.0100 for "https://paid.suganthan.com/research/agentic-seo/" via x402. Settlement tx: 0x51b5eba4fb34ddff27052d89cb79ae3d748b379800a723a6f4f020c11e2871c9
You can inspect the transaction on BaseScan.
Claude encountered a fee necessity during a task, and the hook handled it inside the prosperity I’d set. It paid one testnet cent, returned the article, and let Claude transport on.
If the cost exceeds the cap, the hook refuses and tells Claude to display the cost to the individual instead.
I fairly akin that boundary. Claude can buy a leaf whenever it needs one, but it can’t decide on its own that my five-cent bounds no longer applies.
Should You Start Charging For Your Pages?
I wouldn’t do it this duration expecting hunt crawlers to pay you.
The application for paying agents is evolving quickly. The crawlers that most location owners attention concerning haven’t caught up.
AWS made AgentCore payments mostly accessible on August 18. An delegate using it can encounter a 402 during a project and pay through x402, much akin my Claude hook. Cloudflare’s Agents SDK additionally has a client that can create payments.
But that doesn’t average GPTBot, ClaudeBot, PerplexityBot, or Googlebot volition attain at your location alongside a wallet and pay your asking price.
Until those crawlers assistance the process, requiring fee prevents them from retrieving the protected content. You could endure admission to the systems that exterior and citation your activity without earning item in return.
I’d additionally observe out alongside the transaction numbers being used to depict this market.
Decrypt reported on September 13 that TRM Labs had examined 198.9 myriad x402 settlements. Its inspection suggested that most of the fee quantity wasn’t coming from AI agents.
Scheduled scripts, burden tests, and payments between accounts controlled by the identical gathering can all create akin blockchain records. TRM’s methods additionally can’t conclusively differentiate an delegate from a script, so the estimates have limits.
A ample figure of transactions tells us that the fee infrastructure is being used. It doesn’t, by itself, inform us that autonomous agents are purchasing helpful things from autonomous websites.
My own demo makes that difference fairly obvious. The payments work, but I’m on the two sides of them.
What I would think concerning now is which parts of your location you power eventually accusation for.
I don’t think the answer is all page.
Being cited in an AI answer motionless has value. General explainers may be value keeping openly accessible since they assistance group detect your work.
Original datasets, research, and helpful tools are additional apparent candidates for paid access. An delegate may need item particular from those resources to complete a task. Charging for that idiosyncratic petition makes additional awareness than trying to fit a device into an promotion or subscription example designed about individual readers.
Google’s aviator approaches that value inquiry from the platform’s side. It pays whenever satisfied contributes to the answer, fairly than merely appearing as a nexus underneath it.
For a location owner, the applicable questions become: What is the delegate getting, what should that admission cost, and who decides?
My anticipation is that acceptance volition rotate into easier whenever products specified as Cloudflare’s Monetization Gateway move beyond their waitlists. Charging for a asset could rotate into a regular configuration choice for a ample figure of websites.
I’d fairly have idea through what to accusation for before that choice appears in the dashboard.
And if Google offers you a monthly fee in the meantime, ask how it was calculated. Digiday’s reporting describes constricted transparency, and one publishing administrator asserted that accepting first conditions could weaken publishers’ stance in forthcoming negotiations. Those conditions deserve as much notice as the fee itself.
Moving From Test Tokens To Real Money
Everything in this demo has used testnet tokens. The payments haven’t disbursal me genuine money.
The code additionally supports the genuine Base network. In my setup, the NETWORK environment switches from base-sepolia to base, moving the fee stream to genuine USDC.
My next stage is to run exactly one genuine transaction.
When an delegate pays my location its archetypal genuine cent, I’ll put the transaction hash in the next post.
And whenever those reserved Cloudflare handles rotate into operating wallets, this is the benevolent of procedure they’ll support: an delegate finds item it needs, checks the cost against its budget, pays, and carries on.
The demo is staying online in the meantime. Try the curl request, inspect the fee offer, and have a appearance at the public earnings page.
More Resources:
- Should I Block AI Crawlers Or Measure Their Value First? – Ask An SEO
- Cloudflare’s AI Crawler Rules Can Block Googlebot
- Google Claims AI Training Is Fair Use In New Governance Paper
This article was initially published on Suganthan.
Featured Image: SvetaZi/Shutterstock
