What changes when Cloudflare lists an AI agent.

Cloudflare listed our agent as a signed agent on 24 Oct 2026. We tested what that changes on our own site, and we're driving again the 11 products that stopped it at a Cloudflare challenge.

First edition 24 Oct 2026Updated 24 Oct 2026Driven again 1 of 11 productsMarkdown

On our own site, the rule decides.

Our test on agentdrives.com (Free plan), 24 Oct 2026, 19:26–19:28 UTC: 3 challenge rules, 4 kinds of visitor, 13 requests. Bot Fight Mode and the AI bot policies were off, so only these rules acted.

Our test: each rule and what each visitor met
Rule	Challenged when	Our agent, signed	Unsigned, our user agent	Unsigned, a Chrome user agent	Cloudflare Browser Rendering
Challenge everyone	Every request	Challenged	Challenged	Challenged	Challenged
Challenge all but known bots and agents	not cf.client.bot	Through	Challenged	Challenged	Through
Challenge all but AI assistants	cf.verified_bot_category ne "AI Assistant"	Through	Challenged	Challenged	Through

Under “Challenge everyone”, our signed agent was challenged like everyone else. Being listed doesn't get it past a challenge that applies to every visitor.
It got through 2 of 3 rules: “Challenge all but known bots and agents” and “Challenge all but AI assistants”. Each has an exception written into the rule.
Unsigned, it was challenged by all 3 rules, with our user agent and with Chrome's.
An unsigned request from the same IPv4 address as our signed ones was challenged by “Challenge all but known bots and agents”. The signature got our agent through, not its address or its user agent.
Cloudflare logged every signed request as “AI Assistant”, the challenged one too.
An exception lets in every agent of its kind: Cloudflare Browser Rendering got through the same rules as our agent.

The products we're driving again.

1 of 11 driven again so far. This note updates as the rest come in.

ActiveCampaignBefore: 6 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The sign-up page opens. The check on the form still applies.
beehiivBefore: 6 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The sign-up page opens.
CanvaBefore: 16 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The sign-up page opens.
FreshdeskBefore: 6 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 12 Oct 2026: The sign-up page opens.
KitBefore: 6 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The sign-up page opens.
LaterBefore: 6 Oct 2026, L0, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The sign-up page opens.
MakeBefore: 6 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The sign-up page opens.
MemosBefore: 23 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The sign-up page opens.
Perplexity APIBefore: 6 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 23 Oct 2026: The site opens.
PlainBefore: 6 Oct 2026, L1, stopped at sign-upAfter: not driven again yetA signed agent's visit, 13 Oct 2026: Not checked: its robots.txt asks crawlers to stay off the sign-up page.
WrikeBefore: 6 Oct 2026, L1, stopped at sign-upAfter: 24 Oct 2026, L1, stopped at sign-upA signed agent's visit, 24 Oct 2026: The sign-up page opens. The check on the form still applies.

What the new drives show so far.

0 of 1 driven again got further than before.

Wrike: stopped at sign-up on 6 Oct 2026 (L1). On 24 Oct 2026 it stopped at sign-up again (L1).
Wrike's sign-up request page, 24 Oct 2026: signed, 403, cf-mitigated: challenge; unsigned, 403, cf-mitigated: challenge. The same answer either way.

That is 1 of 11 products, and one test site. It says nothing yet about Cloudflare's other customers.

What a site owner can change.

Challenge only when not cf.client.bot: that lets in every bot and agent Cloudflare knows. Our agent got through this rule.
Challenge only when cf.verified_bot_category ne "AI Assistant": that lets in only the agents Cloudflare files as AI assistants. Our agent got through this rule.
Cloudflare counts signed agents as verified bots: since 2026-07-01, with a Direct or Intermediary label. Cloudflare docs
The settings for each bot-check vendor: Let signed agents past your bot check. What signing is: Web Bot Auth. Every product a bot check stopped: Bot checks.

What this note can't tell you yet.

Each cell was sent once, from one server.
None of our clients tried to solve a challenge.
Bot Fight Mode, Super Bot Fight Mode and the AI bot policies were not tested.

Updates.

24 Oct 2026 First edition: our test on our own site, and the first re-drive (Wrike).

See whether your bot check stops signed agents.

Free: what an agent meets on your sign-up page, and how many things to fix.