Which bot checks let a signed agent in?

Our agent signs every request with its name and a Web Bot Auth signature anyone can check. 95 products met it with a bot check: 77 turned it away, 18 let it in.

A bot check is there to keep out anonymous bots, and a signed agent isn't anonymous. Below, per vendor: how often it stopped our agent, and how to let signed agents through.

10 vendorsSigned drives 2–16 Oct 2026The data

The numbers

Of the 95 products whose bot check met our signed agent.

Same check, different settings.

Google reCAPTCHA, hCaptcha, ALTCHA and Other checks stopped our agent at some products and let it in at others. Per vendor, the most met first: the setting that lets signed agents through.

VendorStoppedLet inHow to let signed agents through
Google reCAPTCHA3610Check the Web Bot Auth signature on the sign-up request and skip reCAPTCHA (or lower the score threshold) for signed agents; or offer a documented sign-up API with email verification.
Check the Web Bot Auth signature on the sign-up request and skip reCAPTCHA (or lower the score threshold) for signed agents; or offer a documented sign-up API with email verification.
Cloudflare270Let verified bots and signed agents past the check on sign-up: in Cloudflare, add a WAF custom rule that skips the bot challenge on your sign-up paths for verified bots and for signed agents (rule field cf.bot_management.signed_agent; since 1 July 2026 signed agents count as verified bots), and render Turnstile only when the request is not from a verified agent.
Let verified bots and signed agents past the check on sign-up: in Cloudflare, add a WAF custom rule that skips the bot challenge on your sign-up paths for verified bots and for signed agents (rule field cf.bot_management.signed_agent; since 1 July 2026 signed agents count as verified bots), and render Turnstile only when the request is not from a verified agent.
hCaptcha81Check the Web Bot Auth signature on the sign-up request (the agent's key directory is public) and skip hCaptcha for signed agents; or offer a documented sign-up API with email verification.
Check the Web Bot Auth signature on the sign-up request (the agent's key directory is public) and skip hCaptcha for signed agents; or offer a documented sign-up API with email verification.
ALTCHA12Skip the CAPTCHA for signed agents (valid Web Bot Auth signature), or offer a documented sign-up API.
Skip the CAPTCHA for signed agents (valid Web Bot Auth signature), or offer a documented sign-up API.
Arkose Labs30Let signed agents (valid Web Bot Auth signature) skip the bot check on sign-up, or offer a documented sign-up API with email verification.
Let signed agents (valid Web Bot Auth signature) skip the bot check on sign-up, or offer a documented sign-up API with email verification.
The product's own check02–
Friendly Captcha01–
HUMAN Security01–
Stytch device fingerprinting10Use Stytch's Web Bot Auth verification to let signed agents through device fingerprinting.
Use Stytch's Web Bot Auth verification to let signed agents through device fingerprinting.
Other checks11Let signed agents (valid Web Bot Auth signature) skip the bot check on sign-up, or offer a documented sign-up API with email verification.
Let signed agents (valid Web Bot Auth signature) skip the bot check on sign-up, or offer a documented sign-up API with email verification.

Let signed agents past your bot check, step by step

Each case, with its drive.

Per vendor: the products, where our agent met the check, and the check as the drive recorded it.

Google reCAPTCHA36 stopped10 let in

reCAPTCHA (invisible)

Google reCAPTCHA (invisible)

Google reCAPTCHA v2 (checkbox)

Google reCAPTCHA v2 (invisible)

Google reCAPTCHA v2

Google reCAPTCHA v2 (image challenge)

  • ApifyStopped at sign up
  • HeapStopped at sign up

reCAPTCHA v2 checkbox

Cloudflare Turnstile (invisible) plus reCAPTCHA v3

Google reCAPTCHA (invisible, escalated to v2 image challenge)

Google reCAPTCHA (invisible, escalating to v2 checkbox)

Google reCAPTCHA (invisible, score)

Google reCAPTCHA (invisible) on the Okta sign-up form, plus Typeform's registration inline hook

Google reCAPTCHA (invisible) on the sign-up form

Google reCAPTCHA (score, captcha_type=google-score)

  • JiraStopped at sign up

Google reCAPTCHA (score, then image challenge page)

Google reCAPTCHA Enterprise (invisible score, then visible checkbox)

Google reCAPTCHA Enterprise (invisible)

Google reCAPTCHA Enterprise challenge page (waf=session) on auth.freshbooks.com

Google reCAPTCHA v2 (invisible, escalated to image challenge); eHawk Talon fingerprint field also on the form

Google reCAPTCHA v2 checkbox

Google reCAPTCHA v2 checkbox (on Backblaze's own 'Security Check' page; reCAPTCHA Enterprise script on the form)

Google reCAPTCHA v2 picture challenge

reCAPTCHA

reCAPTCHA (invisible, v3-style)

reCAPTCHA (script on www.shortcut.com/signup)

reCAPTCHA Enterprise

  • WixStopped at sign up

reCAPTCHA Enterprise (Atlassian sign-up)

reCAPTCHA Enterprise (checkbox)

reCAPTCHA Enterprise (invisible) on Squarespace login

reCAPTCHA v2 (checkbox)

Cloudflare27 stopped

Cloudflare Turnstile

Cloudflare managed challenge (Turnstile 'Verify you are human')

Cloudflare Turnstile (managed challenge)

Cloudflare managed challenge (cf-mitigated: challenge) on reg.wrike.com

Cloudflare managed challenge (interstitial)

  • MakeStopped at sign up

Cloudflare managed challenge (Turnstile 'Verify you are human' interstitial)

Cloudflare managed challenge (Turnstile)

Cloudflare managed challenge (Verify you are human)

Cloudflare Turnstile (invisible)

Cloudflare Turnstile (on Auth0 universal login, login.twilio.com)

Cloudflare Turnstile (on the Clerk sign-up form)

Cloudflare Turnstile (via Clerk bot protection)

Cloudflare Turnstile (visible 'Verify you are human' on the last sign-up step)

Cloudflare WAF block page

hCaptcha8 stopped1 let in

hCaptcha

hCaptcha (image puzzle)

hCaptcha (passive, via Stripe Radar) with Fingerprint visitor data

hCaptcha (script loaded, invisible)

ALTCHA1 stopped2 let in

ALTCHA (proof of work)

ALTCHA proof-of-work (first-party widget, /json/antispam_challenge)

Brave's own proof-of-work captcha ('Verifying you're a human being...')

Arkose Labs3 stopped

Arkose Labs (FunCaptcha)

Arkose Labs (verify.figma.com, figma-api.arkoselabs.com)

The product's own check2 let in

First-party honeypot fields on the sign-up form (field1, status)

hidden honeypot field (telephone)

Friendly Captcha1 let in

Friendly Captcha

HUMAN Security1 let in

HUMAN (PerimeterX) invisible sensor

Stytch device fingerprinting1 stopped

Stytch Device Fingerprinting (magic-link redirect)

  • folkStopped at verify
Other checks1 stopped1 let in

Castle (risk SDK castleSDKV3)

HUMAN

What counts as stopped or let in

A product counts when our agent met its bot check at sign-up, verification or getting a key, in a drive where it signed every request. Stopped: the check turned it away, with or without a visible challenge. Let in: the check was there and our agent got through on its own.

See what an agent sees in yours.

Free, in minutes: the bot check your sign-up puts in front of agents, and the first fixes.

?