What it is
Web Bot Auth is an IETF draft, now draft-ietf-webbotauth-httpsig-protocol-00 (2026-09-01)1. The agent signs each request with HTTP message signatures, tagged web-bot-auth, with a short expiry.2 Its public keys sit in a directory at /.well-known/http-message-signatures-directory.2
A bot check that verifies the signature knows which operator sent the request. The site still decides what that operator may do.
Our agent signs every request it makes. How it signs, and where its keys are.
What our signed agent met
113 of 151 products put a bot check in our signed agent's way. At 19, the check let it through. At 94, a check stopped it on at least one way in.
Signed, not verified: during these drives no bot-check provider listed our agent as a verified bot, so a check could see the signature but had no verified identity to trust.
What a listing at Cloudflare changes, measured on our own site and in new drives: What changes when Cloudflare lists an AI agent.
How to accept signed agents
Allow them where they need to start.
Sign-up, login and the page that makes an API key. Keep your rules everywhere else.3
Keep a puzzle off those pages for verified agents.
A signature doesn't solve a CAPTCHA. The bot-check guide has the settings per vendor.
Check it yourself
Open your sign-up page from a server.
A 403 or a “Just a moment” page means a check at the edge.
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/signupRun a free check.
Our agent signs its requests, so the check shows what a signed agent meets on your sign-up page. Check yours free.