Task types
Every task.type value we accept, and which CAPTCHA family it maps to.
Task type names mirror the anti-captcha and CapSolver vocabulary, so a client written against either works unchanged. Several names map to the same family — that is deliberate compatibility, not duplication, and they are billed identically.
| Family | task.type | Returns |
|---|---|---|
| Cloudflare TurnstileAll modes (managed, non-interactive, invisible). Exact User-Agent supported. |
| Token |
| reCAPTCHA v3v3 and v3 Enterprise, score-based, custom pageAction. |
| Token |
| reCAPTCHA v2Checkbox and invisible, solved via the audio challenge. |
| Token |
| Cloudflare ChallengeClears the "Just a moment…" interstitial and JSD sensor, returns cf_clearance cookies. |
| cf_clearance cookies |
| hCaptchaNon-enterprise widget and invisible mode. |
| Token |
| FunCaptcha / ArkoseArkose Labs FunCaptcha, games answered on a minimal page. |
| Token |
Proxyless and proxy variants
A type ending in ProxyLess solves from our own egress. The variant without that suffix expects proxy fields in the task and routes a real browser through them. Both cost the same: we do not resell proxies, we just use yours. If a hardened target rejects our egress, supplying a residential proxy is usually the fix.
User-Agent control
Pass task.userAgent to pin the browser. Chrome and Edge UAs are served by real Chrome, and a Firefox UA is served by a genuine Gecko engine rather than a rewritten header — which is why Firefox tasks measure a few seconds slower. Always replay a solution with the userAgent returned alongside it; a token minted under one engine and replayed under another is often rejected.
reCAPTCHA and hCaptcha Enterprise variants are accepted under the same names as their standard counterparts. Enterprise widgets with heavy custom parameters are best discussed with us before you build against them.