reCAPTCHA v2, v3 and Enterprise: identify what you need
First identify whether the page uses v2 or v3, then check whether it uses Enterprise. Enterprise can use checkbox or score-based keys; the name alone doesn't tell you which flow you're looking at. solvethree solves standard v3 and Enterprise v3, but not v2.
On this page
What the page actually tells you
| What you find | What it tells you |
|---|---|
| A reCAPTCHA checkbox widget | A checkbox flow, not evidence of score-based v3. Check whether the integration uses the classic or Enterprise library. |
| No checkbox | Inconclusive. v2 can be invisible, so a quiet page doesn't establish v3. |
| Score-based execution with a named action | Evidence of v3. Confirm which library and key configuration the execution uses. |
| api.js | The classic reCAPTCHA library. The filename alone doesn't distinguish v2 from v3. |
| enterprise.js | The Enterprise library. You still need to identify the key type and flow; this doesn't establish v3 by itself. |
<!-- Classic script: investigate whether the page uses v2 or v3. -->
<script src="https://www.google.com/recaptcha/api.js?render=PUBLIC_SITE_KEY"></script>
<!-- Enterprise script: investigate which Enterprise key type is in use. -->
<script src="https://www.google.com/recaptcha/enterprise.js?render=PUBLIC_SITE_KEY"></script>These script tags are identification examples, not solver requests. Inspect the code used by the protected interaction, rather than choosing a task from a script filename alone. A token string by itself won't tell you which flow produced it.
Confirm the hostname and action
For a score-based integration, find the action used by the interaction you need to complete. Don't guess it from a button label or reuse an action from another page. The website can check the expected action on its backend; a token for a different interaction isn't interchangeable.
Confirm the intended hostname and environment too. If you control the integration, check its key configuration to resolve ambiguous page indicators. The public site key identifies the website integration; it isn't the website's verification secret or your solvethree API key.
Use Find the reCAPTCHA action when the page's action isn't obvious.
Choose the matching task
| Confirmed integration | What to do |
|---|---|
| Score-based reCAPTCHA Enterprise | Use the reCAPTCHA v3 Enterprise task. recaptchaType defaults to enterprise-v3; you can also select it explicitly. |
| Classic score-based reCAPTCHA v3 | The gateway accepts recaptchaType set to v3. Select it explicitly rather than relying on the Enterprise default. |
| Checkbox or invisible reCAPTCHA v2, including an Enterprise checkbox flow | Unsupported by solvethree. Changing recaptchaType doesn't turn a v2 flow into v3. |
| Enterprise script, but the flow is still unclear | Confirm the key type and execution flow before creating a task. |
Once you know the variant, set up its site profile before the first solve.
Continue with site profile setup and the reCAPTCHA API integration.
Sources and API reference
Run your first task.
Start with $5 in workspace credit.