# Web Bot Auth explained: verify AI agent requests

> What Web Bot Auth is, how its Signature headers work, how to verify an AI agent's signature, and what a valid signature does not prove.

Canonical: https://heedeo.com/web-bot-auth
Last updated: 2026-11-09

## Web Bot Auth, explained.

Web Bot Auth is an open standard, in draft at the IETF, for agents and bots to sign their HTTP requests. A site can then verify cryptographically which operator sent a request, instead of trusting a user agent string anyone can copy. Heedeo runs a real verifier on heedeo.com, so you can test your own agent against it.

## How it works

- The agent signs each request with HTTP Message Signatures (RFC 9421) using an Ed25519 key.
- Signature-Input lists what was signed and when the signature was created and expires. Signature carries the signature itself.
- Signature-Agent names the operator's origin, for example https://chatgpt.com.
- The operator publishes its public keys as a JWKS at /.well-known/http-message-signatures-directory on that origin.
- The signature's keyid is the key's JWK SHA-256 thumbprint (RFC 7638), so the verifier can find the right key.

## How to verify a signed request

- Parse the three headers and rebuild the RFC 9421 signature base from the signed components.
- Fetch the operator's key directory, with SSRF guards and a cache, and find the key matching keyid.
- Check the Ed25519 signature, and that it hasn't expired.
- Refuse a signature that was already presented once before it expires (replay protection).
- Check the operator against the list of operators you trust.

## What a valid signature does not prove

Anyone can stand up an https origin with a key directory and sign with it. A valid signature proves which origin signed, not that you should trust it. Trust the operators you know, and treat a valid signature from anyone else as unverified.

It also tells you who built the agent, not who it's acting for. The same signed agent can serve a real customer or a farm. That is why Heedeo pairs the signature with what the browser behind it has done: how many identities it has shown you, and what its emails and networks look like.

## Try it against heedeo.com

GET https://heedeo.com/api/visitor returns what heedeo.com sees in your request, including the result of the Web Bot Auth check: present, valid, trusted, verified, the agent origin, the keyid and the reason in plain words. Send it a signed request from your agent and read the answer.

## Questions

### Is Web Bot Auth a standard?

It is an IETF draft built on HTTP Message Signatures, which is a published standard (RFC 9421). Cloudflare proposed it, and agents including ChatGPT agent, Goose, Browserbase and Anchor Browser were among the first to sign with it.

### What is the Signature-Agent header?

It names the origin of the operator that signed the request. The verifier fetches that origin's key directory at /.well-known/http-message-signatures-directory to check the signature.

### Does Web Bot Auth replace bot detection?

It replaces guessing who built an agent. It doesn't tell you what the agent is doing or who it's for, so it is one input to the decision, not the whole decision.

### Who verifies Web Bot Auth today?

Cloudflare uses it for its signed agents program, Fingerprint reads it in its agent detection, and Heedeo verifies it on every signup it scores. You can also verify it yourself with an open-source library.

## Get access

Heedeo is ready. Book a 30 minute demo, and we set it up for your site with you.

- Book a demo: https://cal.com/heedeo/30min?utm_source=heedeo.com&utm_medium=site

## Related

- [Detect and verify AI agents](https://heedeo.com/ai-agent-detection)
- [Heedeo vs Cloudflare Bot Management](https://heedeo.com/vs/cloudflare-bot-management)
- [Heedeo vs Fingerprint](https://heedeo.com/vs/fingerprint)
