What is hCaptcha? The service behind the checkbox.
hCaptcha is a CAPTCHA and bot-detection service run by Intuition Machines, Inc. Websites put its widget on forms such as signups, logins and checkouts. hCaptcha decides whether the visitor is a person, sometimes by showing an image challenge and sometimes without showing anything, and hands the page a token. The site’s server then checks that token with hCaptcha before it accepts the form.
Everything below comes from hCaptcha’s own site and developer docs as they read on November 1, 2026, linked where it is used.
Who runs hCaptcha
hCaptcha is a service of Intuition Machines, Inc., the company named in its privacy policy and in the trademark line at the foot of every hCaptcha page. The about page describes the team as specialists in deep learning and visual machine learning at scale, and describes hCaptcha as “the world’s most widely used independent CAPTCHA service.” That is hCaptcha’s own claim; it publishes no traffic figures to check it against.
The company sells hCaptcha as an alternative to captchas run by advertising companies. Its about page argues that security services from ad companies focus on tracking users across the web, and that bot protection works without doing so.
What a visitor sees
The familiar version is a checkbox inside a small box on the form. Clicking it starts an evaluation. If hCaptcha is confident the visitor is human, the box turns into a green tick and the form can be sent. If it is not, a challenge opens over the page: usually an image grid with a prompt such as “Please click each image containing a motorcycle,” sometimes a drag puzzle or a point-and-click task. Every format is catalogued in hCaptcha challenge types.
hCaptcha’s FAQ puts a typical visit at 3 to 10 seconds, depending on the difficulty mode. It also explains why one challenge is sometimes followed by another: the number depends on hCaptcha’s confidence in the visitor, the site’s difficulty setting and other security factors, and a failed challenge is always replaced with a new one. Why some people get far more challenges than others is covered in why am I getting hCaptcha.
The widget can also run without a checkbox. hCaptcha’s docs separate two ideas
here. Invisible means no checkbox is drawn: the evaluation starts when the
visitor clicks the site’s own submit button, or when the page calls
hcaptcha.execute(), and a challenge appears only if the visitor meets the
challenge criteria. Any plan can use it. Passive is a difficulty setting under
which no visual challenge is ever shown, and only Enterprise has it. Pro and
Enterprise both get a hybrid called “99.9% Passive,” which aims to
challenge fewer than 0.1% of real visitors. The details, and how to spot
a widget that never renders, are in invisible
hCaptcha.
Visitors who cannot do a visual challenge have two routes, according to hCaptcha’s accessibility page. A site can turn on a text-based challenge, offered through the widget’s menu. And any visitor can register on hCaptcha’s accessibility signup page to get a cookie that passes them or gives them an accessibility challenge, depending on the site’s settings. How that cookie behaves today is in the hCaptcha accessibility cookie.
The plans: Publisher, Pro and Enterprise
hCaptcha sells three tiers. The free one is called Publisher in the developer docs and Basic (Free) on the pricing page; they are the same plan. The tiers differ mostly in how much control the site has over who sees a challenge, and in what the site learns about each visitor.
| Publisher (Basic, free) | Pro | Enterprise | |
|---|---|---|---|
| Price | $0 | $139/mo, or $99/mo billed yearly | Quote from sales |
| Included evals | Not listed | 100K a month, then $0.99 per 1K | Not listed |
| Challenge behavior | "Always Challenge" at Easy, Medium, Difficult or Auto | Adds 99.9% Passive (the default for new Pro sitekeys) | Adds full Passive (No-CAPTCHA) mode and rules that decide who gets challenged |
| What siteverify returns | Pass or fail | Pass or fail | Pass or fail plus a risk score and score_reason |
| Look and management | Standard widget | Custom themes, analytics, up to 5 team members | Multi-user dashboard, SAML SSO, reporting APIs, SLAs |
| Beyond the widget | None | None | Risk Insights, Account Defense, fraud protection, Private Learning, backend API protection, pull-based SMS MFA, first-party hosting |
Publisher runs in “Always Challenge” mode with four difficulty levels: Easy, Medium, Difficult and Auto. Every visitor who clicks the checkbox is evaluated, and the free plan has no passive setting to let most of them through untouched. It still includes the protection itself, works in every country, and carries the same GDPR, CCPA, LGPD and PIPL compliance as the paid plans.
Pro adds 99.9% Passive, which is the default for new Pro sitekeys, plus custom themes, analytics and team access for up to five people. The Pro docs note that other security checks, including dynamic proofs of work, run on every request whether or not a challenge appears. Pro comes with a two-week free trial and no card required.
Enterprise wraps a fraud and account-security platform around the
CAPTCHA. The
Enterprise overview lists risk
scores with reasons attached, Risk Insights (session attributes such as VPN or proxy
use), a Rules Engine for deciding who gets blocked or challenged without code
changes, Account Defense for account takeover detection, transaction fraud
protection, Private Learning for models trained on the customer’s own
anonymized data, backend API protection that needs no client-side SDK, and an SMS
multi-factor option where the user texts a code to hCaptcha instead of receiving one.
The feature list on hCaptcha’s homepage
adds control over which challenge types and content are shown, finer difficulty
levels, first-party hosting at hcaptcha.yourdomain.com and legacy
browser support, and the Enterprise
page offers 24/7 SOC coverage through its Managed Defense service. Enterprise sitekeys also attach
per-session rqdata to challenges, covered in
hCaptcha Enterprise rqdata.
Prices, what an eval is and how the bill scales are on hCaptcha pricing.
Where hCaptcha is used
Anywhere a form attracts automated abuse: account signups, logins, password resets, comment and contact forms, checkouts, giveaways and promo redemptions. hCaptcha’s homepage groups its customers into e-commerce, finance, technology, gaming, government, telecom, and privacy-focused messaging, email and VPN services. It also says, without naming them, that more than 60% of major payment platforms use hCaptcha Enterprise.
hCaptcha runs outside the browser too. The docs list native SDKs for iOS, Android and React Native, hundreds of plugins and integrations (WordPress, React, Vue, Angular, Node and more), and Enterprise customers can call it purely server-side. Sites moving from Google’s reCAPTCHA often find the switch small: hCaptcha’s methods are API-compatible with reCAPTCHA v2, and its switching guide comes down to a new script tag, a renamed class and new keys, with callbacks and attributes left as they are. To tell which captcha a given page uses, see how to find an hCaptcha sitekey.
Privacy positioning
Privacy is the main thing hCaptcha sells against reCAPTCHA. Its FAQ says it is “not in the business of selling individually targeted ads,” and its page for visitors says hCaptcha does not care who a user is, only whether they are malicious. The concrete commitments are these:
- Every plan, the free one included, lists compliance with GDPR, CCPA, LGPD and PIPL.
- For sites with EU visitors, hCaptcha acts as a processor: the site that installed it is the controller, and the site’s own privacy policy applies. The privacy policy says hCaptcha uses that data only to provide the service.
- hCaptcha was the first service of its kind to support Privacy Pass in production, according to its Privacy Pass page, and it supports the Private Access Tokens built into Safari.
- Enterprise customers can pre-blind data, for example removing the visitor’s IP through the first-party proxy, and can sandbox the SDK so it cannot read anything else on the page.
- The FAQ reports ISO 27001 certification and a SOC 2 Type II audit, with the full SOC 2 report available to Enterprise customers.
A page that uses invisible hCaptcha should tell visitors so, and the docs suggest this line: “This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.” How hCaptcha’s position compares with Google’s is in hCaptcha vs reCAPTCHA.
How a site verifies a token
When a visitor passes, hCaptcha’s
script writes a token into a hidden form field named h-captcha-response,
and the form posts it to the site’s server along with the rest of the fields. The site has to check that token on its server
before acting on the form: hCaptcha’s
developer guide states that a frontend
callback alone does not authorize the request.
The server sends the token and the site’s secret to
https://api.hcaptcha.com/siteverify as a URL-encoded POST, optionally
with the visitor’s IP and the expected sitekey, and allows the action only when
the JSON reply carries "success": true. This is the example from
hCaptcha’s docs:
curl https://api.hcaptcha.com/siteverify \
-X POST \
-d "secret=YOUR-SECRET&remoteip=CLIENT-IP&response=CLIENT-RESPONSE"
Tokens work once, and the error table lists 120 seconds as the default expiry.
Enterprise accounts get a risk score and score_reason in
the same reply. Every parameter, response field and code sample is on
hCaptcha siteverify, what the token itself
looks like is on the hCaptcha token, and the
failures are listed in hCaptcha error
codes. To watch the whole round trip on a real widget, open the
hCaptcha demo.
hCaptcha reviews: what site owners weigh
Most of what people praise and complain about in hCaptcha follows from the plan table above. The case for it: the free plan has no trial period and no published eval cap, the reCAPTCHA-compatible API makes switching cheap, it works in every country, and the privacy commitments are written into the docs and the policy. Enterprise buyers get a fraud and account-security platform on top of the CAPTCHA.
The complaints come mostly from visitors, and mostly from sites on the free plan. With Publisher there is no passive setting, so anyone the risk check dislikes gets an image challenge, and people on VPNs, privacy browsers or shared networks can see a lot of them. hCaptcha’s answer is the paid passive modes and, on Enterprise, custom threat models that it says avoid blocking users of Brave and Tor. Visitors stuck in a loop of challenges will find fixes in hCaptcha keeps appearing and hCaptcha not working.
For developers who need tokens in automation or testing
If the site is yours and you are testing your own integration, start with hCaptcha’s official test keys. The test sitekey never challenges and always returns the same dummy token, which only the test secret accepts. They are documented with the Enterprise test pairs on hCaptcha test sitekeys.
Test keys stop being enough once the job runs against a real sitekey: an end-to-end
suite on a staging site with production settings, a scraper or monitoring job, an AI
agent that has to complete a form. That is what NoneCap, an
hCaptcha solver service, does. You send the sitekey and the page URL, and the
response carries a real P1_ token for the page to submit as
h-captcha-response, including for invisible and Enterprise
sitekeys.
curl "https://api.nonecap.com/v1/solves?wait=90" \
-H "Authorization: Bearer $NONECAP_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "hcaptcha",
"sitekey": "f5ab1c2d-7e8f-4a9b-b1c2-d3e4f5a6b7c8",
"url": "https://staging.example.com/signup"
}' Billing is from 1 credit per challenge round, charged only when a token comes back. Rates and plans are on the pricing page, the full request and response are in the API reference, and the integration guides cover Python, Playwright, Puppeteer, Selenium and agent loops.
Last updated November 2026.