Docs · Scraping
Auto-detect and solve (v3)
Fetch a URL, detect the reCAPTCHA v3 site key on the page, solve it, return the token — in one call.
POST
/v1/captcha/auto Qcrawl's auto-detect endpoint covers reCAPTCHA v3 invisible only. v2 challenges (checkbox or invisible), hCaptcha, Cloudflare Turnstile, and other challenge types are not supported — we do not plan to add them. For pages where you don't already know the v3 site_key, we fetch the HTML, scan for the key with several known embedding patterns, then run the solver.
Supported
reCAPTCHA v3 invisible (Google's score-based, no user interaction)
Not supported
reCAPTCHA v2 (checkbox or invisible), hCaptcha, Cloudflare Turnstile, FunCaptcha, GeeTest, Arkose Labs, any image-recognition or proof-of-work challenge
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| url | string | yes | — | URL to inspect for a reCAPTCHA v3 challenge. |
| action | string | no | submit | Action parameter to use during solve. |
| proxy | string | no | — | Optional proxy URL. |
Request
curl -X POST https://api.qcrawl.com/v1/captcha/auto \
-H "Authorization: Bearer osk_..." \
-d '{"url": "https://example.com/protected"}'Response
{
"status": "success",
"token": "03AFcWeA6...",
"site_key": "6Lc...",
"time_ms": 612
}Errors
| Code | Meaning |
|---|---|
| 404 | No reCAPTCHA v3 site key was detected on the page. The page may use a different challenge type (v2, hCaptcha, Turnstile) — those are not supported. |
| 500 | Solver could not produce a token. Most often: the detected key was v2 (we are v3-only), the page does not actually use v3, or the upstream rate-limited the request. |