CAPTCHA solving API·16 types·15 live
reCAPTCHA v2 and v3, Cloudflare Turnstile and Clearance, Arkose FunCaptcha, GeeTest, DataDome and Imperva — through a single JSON endpoint. Built for web scraping, QA automation and accessibility testing.
The request never changes — only task.type. 15 are live; every latency below is published as measured, including the slower ones, and a type with no window behind it yet prints a dash rather than a guess.
Every number on this page comes from the same catalogue the API reads, so a median cannot be flattering here and honest in the docs. 6 things this service does that you can verify on your first day.
A provisional hold is placed when a solve starts and released the moment it fails. A blocked IP, an unsolvable challenge, a timeout — none of them are billed, and the response says so in its own cost field. Nothing to reconcile at the end of the month.
errorId != 0 → cost "$0.0000"The request shape never changes. Going from reCAPTCHA to FunCaptcha is a different task.type and the fields that type takes — same route, same auth, same response. The call is synchronous by default, so there is no job id to store and no polling loop to write unless your workers actually want one.
POST /v1/getResult · task.typeMedians are measured and shown as measured. reCAPTCHA Mobile sits at 173ms and Cloudflare Clearance at 17s, both on the same table. A latency figure that only ever shows the best case is not a figure.
173ms … 17s median12 of the 15 live types carry a measured 30-day success rate; the other 4 public types print a dash instead of borrowing a neighbour's number. A type with no window behind it yet has no single figure that would be honest, and an invented one is worse than none.
12/15 live rates publishedEvery account gets a test key alongside the live one. It solves a synthetic challenge, returns a well-formed response in about two seconds and never touches your balance — the real code path, safe to run in CI on every commit.
same endpoint · zero costTop up in USDT, USDC, BTC, ETH, BNB, SOL and 7 more, across 25 asset and network combinations — stablecoins on TRC20, ERC20, BEP20, Base, Polygon, TON, plus a privacy chain. No card on file, no invoice, no minimum, and no subscription you have to cancel — you pay for solves and nothing else.
25 networks · no minimumPOST /v1/getResult holds open for the length of the solve and returns the finished result — no polling loop, no job id to track. Set a client timeout that covers the slowest type you use. Workers that cannot wait post to /v1/createTask and collect from /v1/checkTask.
# pip install voidcaptcha
from voidcaptcha import VoidCaptcha
client = VoidCaptcha("void_a1b2c3d4e5f60718293a4b5c6d7e8f90")
result = client.recaptcha_v3(
url="https://example.com/login",
site_key="6LdyC2cUAAAAACGuDKpXeDorzUDWXmdqeg-xy696",
action="login",
proxy="proxy.example.com:9090:user:pass",
)
print(result.value){
"errorId": 0,
"status": "ready",
"solution": {
"token": "03AGdBq27X4…",
"userAgent": "Mozilla/5.0 …"
},
"cost": "$0.0008",
"balance": "$411.24",
"elapsedMs": 4820
}Start metered — it is the default and needs no decision. Once a type is carrying steady volume, a subscription buys unlimited solves of it per thread instead, at a price derived from the metered one.
Top up a balance and it draws down one solve at a time. Nothing to commit to and nothing to cancel — every account starts here.
Name the types you want covered and buy concurrency for a period. Solves of those types stop touching the balance entirely — they are unlimited for as long as the period runs.
The subscription price is derived from the metered one, so the two can never drift apart. Beyond 224,000 solves the subscription simply keeps going — coverage is unlimited for the types it names, and anything outside them falls back to metered on the same call. No solve is ever billed twice.
13 of the 16 public types can be put on a subscription today, and PerimeterX · HUMAN joins them on release. Kasada and Akamai Bot Manager are metered only. Subscriptions are set up from billing in the dashboard.
The metered rate for every public type, with the measured median and success rate beside it. Failures are refunded automatically. Priced in USD, settled across nine networks.
| CAPTCHA type | task.type | Median | Success | USD / 1k | Thread-day | USDT |
|---|---|---|---|---|---|---|
| reCAPTCHA v2 | ReCaptchaV2 | — | — | $0.50$0.0005 eachEnterprise $1.00 | $2.40per thread · day | 0.50 |
| reCAPTCHA v3 | ReCaptchaV3 | — | — | $0.80$0.0008 eachEnterprise $1.50 · Max $2.00 | $3.84per thread · day | 0.80 |
| reCAPTCHA Mobileno proxy | ReCaptchaMobile | — | — | $1.00$0.0010 each | $4.80per thread · day | 1.00 |
| Arkose FunCaptcha | FunCaptcha_Invisible | — | — | $2.00$0.0020 each | $9.60per thread · day | 2.00 |
| DataDome | datadome_Interstitial | — | — | $2.00$0.0020 each | $9.60per thread · day | 2.00 |
| Imperva Incapsula | IncapsulaToken | — | — | $1.90$0.0019 each | $9.12per thread · day | 1.90 |
| Cloudflare Turnstileno proxy | Turnstile | — | — | $1.20$0.0012 each | $5.76per thread · day | 1.20 |
| GeeTest | GeetestV4 | — | — | $1.00$0.0010 each | $4.80per thread · day | 1.00 |
| Hunt Captcha | HuntCaptcha | — | — | $1.50$0.0015 each | $2.70per thread · day | 1.50 |
| CaptchaFox | CaptchaFoxTask | — | — | $1.20$0.0012 each | $5.76per thread · day | 1.20 |
| Image to Textno proxy | ImageToTextTask | — | — | $1.00$0.0010 each | $4.80per thread · day | 1.00 |
| Kasada | KasadaCdTask | — | — | $0.20$0.0002 eachKasadaTask $2.00 | —metered only | 0.20 |
| Cloudflare Clearance | CFClearance | — | — | $1.20$0.0012 each | $2.16per thread · day | 1.20 |
| Akamai Bot Manager | akamai_abck | — | — | $2.00$0.0020 eachakamai_sbsd $2.80 | —metered only | 2.00 |
| Amazon AWS WAF | awsToken | — | — | $1.45$0.0014 each | $6.96per thread · day | 1.45 |
| PerimeterX · HUMANsoon | PerimeterX | — | — | $2.50$0.0025 each | $12.00per thread · day | 2.50 |
USD / 1k is metered: charged per successful solve, drawn from your balance, failures refunded. Thread-day is the subscription rate — unlimited solves of that type per concurrent thread, priced 40% under the metered equivalent at 8,000 solves a thread-day. A dash means the type is metered only.
…and 9 more at checkout — 13 currencies across 25 asset and network combinations.
no card · no invoice · no minimum
Answered from how the service actually behaves, including where the answer is a limitation.
16 types through a single JSON endpoint: reCAPTCHA v2, reCAPTCHA v3, reCAPTCHA Mobile, Arkose FunCaptcha, DataDome, Imperva Incapsula, Cloudflare Turnstile, GeeTest, Hunt Captcha, CaptchaFox, Image to Text, Kasada, Cloudflare Clearance, Akamai Bot Manager, Amazon AWS WAF, PerimeterX · HUMAN. 15 are live and carrying traffic; the rest are marked beta or soon on the coverage table, with their real status rather than a launch date.
See the coverage table →Nothing leaves your balance. A failure is a well-formed response carrying a non-zero errorId, a stable errorCode such as ERROR_IP_BLOCKED, and cost "$0.0000" — the provisional hold placed when the solve started is released the moment it fails. The error reference states for every code whether retrying is worth attempting, which is the part most integrations get wrong.
Error reference →For every public type except reCAPTCHA Mobile, Cloudflare Turnstile and Image to Text, yes. A token or cookie is issued to a session and a session is identified partly by its exit IP, so a solve run from our network and presented from yours is rejected however good it was. Use a sticky session — an exit that rotates mid-solve looks exactly like a hijacked one.
Proxy formats and pools →It varies by type, and the measured median for each is published on its own page as soon as there is one to publish — a dash until then, rather than an estimate. POST to /v1/getResult and the response arrives when the solve does, so set a generous client timeout rather than leaving your HTTP library on its default: a browser-challenge type can take an order of magnitude longer than a score-based one. Workers that cannot hold a connection open that long can post the same task to /v1/createTask and collect it from /v1/checkTask instead.
Yes: 100 free solves once you confirm your email, on any type — real tokens from the live solvers, one trial per person. Your first top-up also gets a bonus of +50% up to $25, added automatically. Every account also gets a test key that returns a well-formed response without touching your balance, so you can build and run the integration in CI for free. Paid solves start at $0.20 per 1,000.
Create an account →One solve in flight. Accounts are limited by concurrency rather than by requests per second, which suits a synchronous API better: ten concurrent solves is the metered default, and exceeding it returns ERROR_THREAD_LIMIT with HTTP 429 — worth retrying with backoff rather than treating as an outage. A subscription buys its own pool of 1 to 500 threads, and solves it covers draw on that pool instead of the metered limit.
Metered draws a balance down per successful solve. A subscription buys unlimited solves of the types you name for a fixed period, billed per concurrent thread and priced 40% below the metered equivalent at 8,000 solves per thread per day. Buy it weekly, monthly, or for a custom 3 to 365 days, account-wide or scoped to one key. Anything the subscription does not name still falls back to metered on the same call, a covered type never touches your balance, and no solve is ever charged twice.
14 of the 16 public types today: TLS API, reCAPTCHA v2, reCAPTCHA v3, reCAPTCHA Mobile, Arkose FunCaptcha, DataDome, Imperva Incapsula, Cloudflare Turnstile, GeeTest, Hunt Captcha, CaptchaFox, Image to Text, Cloudflare Clearance, Amazon AWS WAF. PerimeterX · HUMAN is eligible too, and can be covered once open to traffic. Kasada and Akamai Bot Manager stay metered only.
No. A solve record keeps the host of the target and never the full URL or its query string, alongside the type, the outcome, the elapsed time and what it cost. Your API key is stored only as a SHA-256 hash, which is also why a key can be shown to you exactly once and never recovered afterwards.
From the keys page in your dashboard. Rotating issues a new key and revokes the previous one immediately — there is no grace period, so deploy the new key first if you cannot tolerate failed calls, or create a second key, migrate to it, then revoke the old one. Calls made with a revoked key return ERROR_KEY_INVALID.
Authentication docs →Telegram, at @VoidCaptchaSupport — it is the fastest way to reach us and someone is usually there within minutes, at any hour. It is the right route for a type that is failing or a site that will not solve. For anything tied to your account — billing, a refund, a specific solve you want looked at — open a ticket from your dashboard instead, so there is a record attached to the account. [email protected] also works. We never message you first, and we never ask for your API key.
Message us on Telegram →Anything else — message us on Telegram for the quickest answer, or [email protected]. The documentation answers most of it first.
A live key the moment you verify, and a test key that costs nothing. No card, no sales call. Your first token lands in about a minute.