Definition
Web Bot Auth is a way for bots and AI agents to prove who they are by cryptographically signing each HTTP request, using HTTP Message Signatures (RFC 9421). The operator publishes its public keys, and a website or its firewall checks the signature against them. It is being standardized in an IETF working group and is not yet an RFC.
Why it matters
A bot's name in the User-Agent header is a claim anyone can copy. IP checks help, but an IP address only tells you which network a request came from. A signature is much harder to fake. Only the holder of the private key can produce one that matches the operator's published public key.
That gives you a reliable way to let a real shopping agent through your firewall while still blocking requests that use the same name but fail verification.
How it works
Cloudflare's documentation describes the setup:
- The operator generates an Ed25519 key pair and keeps the private key.
- It publishes the public key in a key directory at
/.well-known/http-message-signatures-directoryon its own domain. - Each request carries three headers:
Signature-Agent, which points to that directory,Signature-Input, which lists what was signed and when it expires, andSignature, which carries the signature itself.
The receiving site, or a service in front of it, fetches the key and checks the signature following RFC 9421.
Several agents sign today. OpenAI's documentation says ChatGPT signs certain automated browser requests with a Signature-Agent value of "https://chatgpt.com". Google says it is experimenting with Web Bot Auth using the https://agent.bot.goog identity.
The standard itself is still in progress. At the time of writing, the IETF webbotauth working group's active document is draft-ietf-webbotauth-httpsig-protocol-01, dated 2026-10-29. It is an Internet-Draft, not an RFC, so details can still change.
Example
A request arrives with these headers (shortened):
Signature-Agent: "https://chatgpt.com"
Signature-Input: sig1=(...);created=...;keyid="...";expires=...
Signature: sig1=:...:
Your firewall fetches the public keys from chatgpt.com's key directory and checks the signature. If it matches, the request is verified as coming from ChatGPT's agent. If it fails, treat it as unverified. Sill checks Web Bot Auth signatures on Cloudflare and WordPress installs, for agents that sign. For a fuller guide, read Web Bot Auth: how AI agents sign their requests.
Sources
- Cloudflare: Web Bot Auth · checked 16 Nov 2026
- IETF webbotauth working group documents · checked 16 Nov 2026
- OpenAI: Agent access (ChatGPT signed requests) · checked 16 Nov 2026
- Google: User-triggered fetchers · checked 16 Nov 2026