Migration guide
Switching from NextCaptcha
Same task API, two letters apart in the name. They are cheaper on reCAPTCHA v2 and Turnstile; here you get 33 types on one key with p50 and p95 published.
API compatibilityDrop-in — change the base URL
What they do well
- The cheapest reCAPTCHA v2 rate published by anyone in this comparison: $0.50 per 1,000, against our $1.50. If reCAPTCHA v2 is the whole workload, they are hard to beat on price.
- Turnstile at $0.60 per 1,000, roughly half what CapSolver and CapMonster charge and well under our $2.18.
- Speed targets that are specific and falsifiable — under 3s for v3, Mobile and Turnstile, under 6s for v2 — and every result carries createTime and endTime so you can check the claim yourself.
- reCAPTCHA Mobile as a first-class task type. Almost nobody else ships one, and for mobile app flows it is a genuine reason to pick them.
- They cloned the Anti-Captcha convention faithfully and added almost nothing: clientKey in the body, createTask / getTaskResult, the same envelopes. That makes it one of the cleanest API surfaces in the category.
- Open-source SDKs for Python, Go and C#, per-type parameter tables in the docs, a free trial with no card, and pay-only-for-success billing.
Where they fall short
- The catalogue is reCAPTCHA variants plus Cloudflare Turnstile. Their own docs list eleven task types and their own price page lists five rows.
- No hCaptcha, no image-to-text or OCR of any kind, no GeeTest, no DataDome, no Cloudflare interstitial, no AWS WAF, no Arkose, and none of the Chinese-market types. One new challenge on a target site and you are shopping for a second vendor.
- Their marketing says they support all captcha types while their documentation and price page show eleven. Both pages are public and can be read side by side.
- Their docs contradict themselves on capitalisation: the sidebar says ReCaptchaV2TaskProxyLess and the request example says RecaptchaV2TaskProxyless. That is the kind of thing that returns a silent 400 at 3am.
- Cryptocurrency only. If you need an invoice, a card receipt or a procurement trail, that is a hard stop regardless of the rate.
- One documented report of their own WAF blocking a paying customer's server IP at around ten parallel requests every fifteen minutes, with support unable to resolve it.
- Seven Trustpilot reviews, none in the past year. There is very little outside evidence either way about how the service holds up under sustained production load, and their own guidance tops out near 1,000 concurrent threads before you have to negotiate.
[ 02 ]Side by side
Side by side
| NextCaptcha | NexCaptcha | |
|---|---|---|
| Published pricing | Five rows: reCAPTCHA v2 $0.50, v3 $0.60–$1.00, Turnstile $0.60. Crypto payment only. | 33 types, $0.75 to $4.49 per 1,000, one USD price list for every visitor. |
| Published latency | Targets, not percentiles: under 3s for v3 and Turnstile, under 6s for v2. | p50 and p95 per type. Overall p50 4.8s, p95 11.2s. |
| Published success rate | 99% stated for reCAPTCHA v2. Nothing published for the other four rows. | Published per type. 99.4% overall, measured on tokens the site accepted. |
| What counts as a solve | A token returned by the API. | The target site accepting the token. Returning one is not enough. |
| Failed-solve billing | Failed requests are not charged, stated on their price page. | Rejected, failed and timed-out solves are refunded automatically within the hour. |
| API compatibility | createTask / getTaskResult, clientKey in the body. Type casing differs between their own pages. | Same envelope, same field names. The base URL and the type casing are the change. |
| Support response | No published response target. One WAF-block report left unresolved. | 24/7 from engineers. Median first response 7 minutes on Telegram. |
[ 03 ]The code change
The code change
NextCaptcha is a faithful Anti-Captcha clone: JSON POST to createTask and getTaskResult, clientKey in the body, the same {errorId, taskId} and {errorId, status, solution} envelopes, and solution.gRecaptchaResponse on the way back. The field names are identical to ours and the type names differ only in casing, which their own documentation is inconsistent about. Read the hostname in the diff below character by character: NextCaptcha is nextcaptcha.com and we are nexcaptcha.net, two unaffiliated companies whose names are two letters apart.
How to migrate
- 01Point your existing client at api.nexcaptcha.net and swap the API key — the request envelope, the field names and the response shape are already identical.
- 02Do one find-and-replace on task type casing: their ReCaptchaV2TaskProxyLess is our RecaptchaV2TaskProxyless. Search for both spellings, because their own documentation uses both.
- 03We do not publish a reCAPTCHA Mobile task type. If any of your traffic is mobile-app reCAPTCHA, keep that flow on NextCaptcha — it is the one thing on this page we do not replace.
- 04If a dashboard reads createTime and endTime off the result, check those fields against our response before you cut over. Every response also carries the measured solve time in a header.
- 05Run both in parallel on a traffic split and compare accepted rate per type on your own targets. Their reCAPTCHA v2 is $0.50 against our $1.50, so the move has to earn that gap on your numbers, not ours.
[ 04 ]Questions about this one
Questions about this one
No. NextCaptcha is nextcaptcha.com, we are nexcaptcha.net, and the two are unaffiliated. The names are two letters apart, which is worth checking before a hostname goes into production config — and worth knowing if you reached this page while looking for them.
Yes, and for reCAPTCHA and Turnstile flows it is about an afternoon: one base URL, one key, one find-and-replace on type casing. Keep both clients alive on a traffic split until the accepted rate on your own targets says the move was worth it. Budget longer only if you depend on reCAPTCHA Mobile, which we do not publish, or on their websiteInfo score parameter, which has no direct equivalent here.
One find-and-replace. The words are the same and only the casing differs: ReCaptchaV2TaskProxyLess there, RecaptchaV2TaskProxyless here. Search for both spellings, because their sidebar and their request example disagree with each other.
No. reCAPTCHA v2 is $0.50 per 1,000 there and $1.50 here, Turnstile is $0.60 against $2.18. If reCAPTCHA and Turnstile are your entire workload and they are working, staying is the rational choice. What the difference buys is the other 31 captcha types on one key, p50 and p95 published per type, and billing tied to whether the target site accepted the token. The moment a target adds hCaptcha, GeeTest, DataDome or a Cloudflare interstitial, the comparison stops being about price.
Solve your first thousand on us.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.