Web Bot Auth gives a store a reliable answer to one question: which company is operating this AI agent? The agent signs each request with a private key, publishes the matching public key, and your server or CDN checks the signature. That beats trusting a User-Agent string anyone can copy. What it does not tell you is who the shopper is or what they approved. This guide explains how it works and what a store can do with it, based on the IETF draft and vendor posts as of November 2026.
- Current draft revision (29 Oct 2026)
- -01
- Headers a signed request carries
- 3
- Cloudflare signed agents launch
- Aug 2025
- What a signature proves
- Operator only
Why do stores need to verify agents at all?
A shopping agent can be a welcome customer or a scraper wearing the same name. Today most stores identify bots by User-Agent string, which is trivial to fake, or by IP range, which works only when the vendor publishes ranges. OpenAI publishes IP lists for its crawlers and ChatGPT-User, according to its bot documentation, and Anthropic publishes the IPs Claude Duet browses from. Many agents publish neither.
Retailers are starting to demand identification. Amazon's Agent Terms, published 30 May 2025, require shopping agents to identify themselves as "Agent/[name]", and Amazon cited Meta Muse's failure to identify itself when it blocked the agent on 20 September 2026. See Amazon's agent terms. Signatures are a harder-to-fake version of that idea.
How does Web Bot Auth work?
The IETF draft builds on HTTP Message Signatures (RFC 9421). Revision -01 was published on 29 October 2026 by authors from Cloudflare and Google.
- Operator publishes keysA JWK Set at /.well-known/http-message-signatures-directory on its own HTTPS domain.
- Agent signs the requestCovering the target authority or URI, created and expiry times, key ID and a tag of web-bot-auth.
- Agent sends three headersSignature, Signature-Input and Signature-Agent (the operator's directory URL).
- Your server fetches the keyDirectly from the Signature-Agent URL, without following redirects.
- Your server verifiesIf the signature checks out, the request really comes from that operator.
A few details matter for implementers:
- Algorithms. The draft covers RSA, EC and Ed25519 keys; its test vectors use RSASSA-PSS with SHA-512 and Ed25519.
- Replay window. A signature that covers only the authority can be replayed to that site until it expires, so keep expiry windows short and check the
createdtime. - Revocation. The draft defines none. A removed key stops working when your cache refreshes.
- Failures. A failed key lookup is not proof that a key is invalid, so treat lookup errors as "unverified", not "malicious".
- Agent signs request
- Signature-Agent URL
- Key directory
- Your verifier
- Allow, rate-limit or challenge
What does a signature not prove?
The draft says plainly that it "does not authenticate human users". It also does not establish whether the operator is honest, benign or authorised. A valid signature tells you "this request came from OpenAI's agent infrastructure" or "from Browserbase". It does not tell you that a real shopper asked for it, how much they agreed to spend, or that the agent is not being steered by a malicious page. The draft also notes that stable identifiers let operators be correlated across sites.
Questions of shopper authority are handled elsewhere: by checkout protocols such as ACP and UCP, by payment tokens with spending limits, and by mandates in Google's AP2. See ACP vs AP2 vs UCP.
What are Cloudflare signed agents?
Cloudflare announced its signed agents category on 28 August 2025. Signed agents are agents generally directed by an end user, sign their requests with Web Bot Auth and follow Cloudflare's signed-agent policy. They sit alongside Cloudflare's existing verified bots programme, which continues.
The first signed agents named were:
| Agent | Operator |
|---|---|
| ChatGPT agent | OpenAI |
| Goose | Block |
| Browserbase | Browserbase |
| Anchor Browser | Anchor |
Cloudflare's own Browser Rendering also appears in the category. Anyone can see the list and traffic patterns in Cloudflare Radar's bots directory, and operators apply through a bot submission form.
For store owners on Cloudflare, the post said Enterprise customers would be able to act on signed agents as a group in security rules, similar to verified bots, with the dashboard field arriving "soon". Reports differ on when this reached production (some point to August 2025, others to March 2026), so check your own dashboard. On 5 November 2026 Cloudflare announced a "Trusted Agent Delegation" coalition; we have not found published technical details beyond the announcement.
How do card networks use agent signatures?
Visa's Trusted Agent Protocol, announced on 14 October 2025 and built with Cloudflare, uses cryptographic agent signatures so merchants can tell trusted agents from bad bots. Beyond identity, it carries agent intent, consumer recognition and optional payment information. Feedback partners included Adyen, Checkout.com, Coinbase, Microsoft, Shopify, Stripe and Worldpay. Mastercard Agent Pay, launched in April 2025, requires agents to be registered and verified. See Visa Intelligent Commerce and Mastercard Agent Pay.
For a merchant, this means verification may increasingly arrive through your payment provider and CDN rather than code you write.
What should a store actually do?
Pros
- Proves the operator without trusting User-Agent strings
- Open standard; works with any CDN or server
- Lets you allow good agents while challenging unknown bots
Cons
- Draft standard, still changing
- Says nothing about the shopper or their approval
- Many agents do not sign requests yet
A sensible policy for most stores:
- Measure first. Log the
Signature-Agentheader and verification result alongside User-Agent for a few weeks. Our traffic tracking guide covers this. - Allow verified agents through checkout. Exempt signed, verified agents from CAPTCHAs that would otherwise force them to hand the task back.
- Rate-limit, do not ban, unverified agents. Real shoppers use agents that do not sign yet.
- Keep robots.txt consistent. A signature does not override your stated policy. See robots.txt and AI shopping agents.
- Keep fraud checks on payment. Verification of the agent is not verification of the card holder.
Bottom line
Web Bot Auth is the most practical way today to tell real AI agents from impostors, and if you use Cloudflare you may get much of it without writing code. Use it to decide which agents get a smooth path, not to decide which shoppers to trust. For the bigger picture, see making your store agent-ready.



