If you’ve asked “how do I know that request claiming to be an AI shopping agent actually is one” — the answer forming across the industry right now is Web Bot Auth: a way for a bot or agent to cryptographically sign its own HTTP requests, instead of asking a site to trust a spoofable User-Agent string or IP address. It started as a crawler-verification spec. In 2026 it’s become the identity layer that Visa, Mastercard and American Express are building agentic checkout on top of — which makes it relevant to merchants, not just security teams.

What it actually does

Web Bot Auth is built on RFC 9421 (HTTP Message Signatures): an agent signs each request with a private key, attaches a Signature-Agent header pointing to a public-key directory, and the receiving site fetches that directory to verify the signature. No shared secret, no allowlisted IP range to keep in sync — just a signature the origin can check per request. It’s now a chartered IETF working group (webbotauth), with a standards-track authentication spec due to the IESG by April 2026 and a Best Current Practice document on key management and deployment due August 2026 (IETF webbotauth charter). Cloudflare originated the approach in 2025 and documents the mechanics in its bot-verification reference.

Who’s actually verifying it

The news isn’t the cryptography — it’s that verification has spread past Cloudflare to the rest of the stack a store might sit behind:

  • AWS WAF, Vercel, Akamai and HUMAN Security now verify Web Bot Auth signatures, and Amazon’s own Bedrock AgentCore Browser signs outbound agent requests with it in preview specifically to skip CAPTCHAs at sites that recognize the signature.
  • Google published its own guide, “Google’s Guide to Authenticating Requests with Web Bot Auth” (marked Experimental), including a public-key directory at agent.bot.goog/.well-known/http-message-signatures-directory — Google is now a first-party participant in the spec, not a bystander.
  • Cloudflare and GoDaddy partnered to pair Web Bot Auth’s cryptographic signatures with GoDaddy’s DNS/PKI-based Agent Name Service, extending crawler management and agent-identity verification to GoDaddy’s much larger base of smaller sites.

Why this matters more than “just” bot management

The part that should get a merchant’s attention: Visa’s Trusted Agent Protocol (TAP) and Mastercard’s Agent Pay both authenticate AI shopping agents using Web Bot Auth as the signing layer, and American Express is building its agentic-commerce offering on the same foundation (Cloudflare — “Securing agentic commerce: helping AI Agents transact with Visa and Mastercard”). In practice: an agent registers with a payment network, its public key lands in that network’s directory, and it signs its checkout request with the matching private key — letting a merchant’s site tell “a Visa-registered shopping agent” apart from an unverified scraper before the payment step, the same way ACP and UCP already split checkout into two non-interoperable rails.

What to check on your own store

  • Does your CDN/WAF (Cloudflare, Akamai, AWS WAF, Vercel, HUMAN Security) have Web Bot Auth verification turned on, and is it configured to let signed agents through rather than treat all automated traffic the same?
  • If you accept Visa or Mastercard, is your checkout flow prepared to see Web Bot Auth-signed agent requests arrive under TAP/Agent Pay, rather than only human, cookie-based sessions?
  • Is this on your radar as a Pillar 1 (access) check, separate from — but feeding into — whether an agent can actually complete a purchase once it’s let in? That transaction-level gap is what an AgentReady scan checks directly.

Sources

As of July 2026. Web Bot Auth is still a draft IETF spec — check the working group’s datatracker page for the current milestone status before making implementation decisions.