Standard · Trust
Web Bot Auth
An agent signs each request, and you verify who it is from its published keys.
What it is
Each request from an agent carries a digital signature. The agent publishes its public keys at /.well-known/http-message-signatures-directory. A site checks the signature and knows the request really came from that agent, not from someone using its name.
An analogy
At a glance
- Owner
- IETF working group
- Maturity
- Emerging draft-ietf-webbotauth-httpsig-protocol-01, October 2026. Already used by Cloudflare’s signed agents, AWS WAF, and Visa’s and Mastercard’s agent protocols. Built on HTTP Message Signatures (RFC 9421).
- Where it lives
- IETF draft
- Framework domain
- Trust: Be trusted
- What it serves
- Tell real agents from impostors
- Allow trusted agents through your defenses
Who should care
The roles this standard touches most. See all the roles on the personas page.
- Legal, risk and security. Set the policies: which agents may do what, identity, data, disclosure and liability.
- Engineering and product. Build the access, data, endpoints and actions that agents use, on open standards.
How to adopt it
- 1
Check whether your CDN or firewall already verifies signed agents.
- 2
Decide which verified agents get different treatment.
- 3
If you run an agent, sign its requests and publish your key directory.
The Institute’s view
The most credible route to knowing who an agent is. It is still an IETF draft, so use the verification your CDN or firewall provides rather than writing your own.
Standards change fast. Last reviewed November 2026.