What it is
An agent signs its requests with Web Bot Auth. A vendor then verifies the operator and adds it to its list. On Cloudflare an operator applies through the Bot Submission Form, with Request Signature as the way to verify it.1
Since 1 July 2026 Cloudflare counts signed agents as verified bots.2 Its default bot settings leave verified bots alone on every plan.2 HUMAN gives an agent that signs every request a high trust level.3
What a known signed agent met
For each product we also fetch its sign-up page as a signed agent Cloudflare already knows, and compare it with an agent on a server.
The sign-up page opened for that signed agent at 112 of 131 products where we fetched it.
The difference shows where a check stood at the edge: 10 of 13 products that stopped agents on a server before the sign-up page opened it for the known signed agent.
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.
How to let them in
Leave verified bots out of your own block rules.
On Cloudflare, add the verified-bot field to each custom rule on sign-up, login and the key page:
cf.bot_management.verified_bot (boolean)4.(your rule's expression) and not cf.bot_management.verified_botCheck your AI bot policy.
New Cloudflare domains since 15 September 2026 block agents on pages that show ads.5 Allow them on the pages where they sign up.
Do the same on your other vendors.
The bot-check guide has the setting for Vercel, Akamai, DataDome, HUMAN and AWS WAF.
Check it yourself
Read your security events.
Look for requests on your sign-up page from verified bots. A block or a challenge there is a rule to change.
See it on your product's page.
Each product page here shows who gets in: an agent on a server, a known signed agent and an agent in a browser.