What happened
AWS’s AgentCore Browser docs, fetched 23 Oct 2026 (the page carries no date), now name DataDome and F5 as bot-control vendors that support its Web Bot Auth, next to Cloudflare, HUMAN Security and Akamai Technologies: (Amazon Bedrock AgentCore docs). The feature is in Preview and built on the draft IETF Web Bot Auth protocol. AWS says: The authentication works transparently - once enabled, your agents can browse websites protected by these services with reduced friction.
The same page says owners keep the last word: Domain owners retain full control over their bot policies and may block, monitor, or rate-limit agent traffic regardless of cryptographic signatures
(AWS docs1).
What our drives saw
Our agent signs every request with Web Bot Auth, across 148 of 148 drives up to 22 October 2026. 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.
Of the vendors on the AWS list, our signed agent met these on its way in:
| Vendor | Met at | Stopped it | Let it in |
|---|---|---|---|
| Cloudflare | 34 of 148 | 34 of 34 | 0 of 34 |
| DataDome | 1 of 148 | 1 of 1 | 0 of 1 |
| Akamai Bot Manager | 1 of 148 | 1 of 1 | 0 of 1 |
| HUMAN Security | 1 of 148 | 0 of 1 | 1 of 1 |
Each of the other vendors in the table came up at the one product where our agent met it. DataDome stopped it there with a visible challenge, and Akamai Bot Manager stopped it with none shown. HUMAN Security let it through at Webflow, with no challenge shown. The full provider picture is in which bot checks stop AI agents.
What it means
For owners: a vendor on the AWS list can check a signed agent’s identity, and your bot policy still decides what happens next. DataDome blocks agents that aren’t authenticated by default and counts a Web Bot Auth signature as authentication (DataDome docs). Whether an authenticated agent gets in is then the DataDome customer’s own bot policy (DataDome docs). If you run DataDome and want signed agents at your sign-up, that policy is the place to allow them.
For builders: AWS says AgentCore registers with bot control vendors and gives them its public keys. To be verified at Cloudflare, a signed agent registers through its Bot Submission Form with request signatures as the method (Cloudflare docs). Our earlier note on Cloudflare and verified bots has the Cloudflare side.
What we don’t know
AWS doesn’t say when DataDome and F5 support began, or whether either lets AgentCore traffic in by default or only under a policy the site owner sets. DataDome counts a signature as authentication, yet it stopped our signed agent: our records show the stop, not which part of that product’s policy made it. Our facts carry no count for F5. Our agent is not AgentCore, so our counts show what a signed, unverified agent met, not what AgentCore’s registered traffic meets.
What we’ll do
Next week we check our recorded attempts for any product that sits behind F5 and add an F5 count to our facts if one does. The next drives of the products behind DataDome and Akamai Bot Manager show whether those stops still hold; how we drive.