Switch from DeathByCaptcha to CaptchaAI for thread pricing and a simpler API.
DeathByCaptcha has been solving CAPTCHAs for over 17 years. CaptchaAI adds the full-page Cloudflare Challenge and BLS, which DeathByCaptcha doesn't list — with a plain API-key REST integration (no SDK) and thread-based pricing that flattens at scale.
# DeathByCaptcha: username/password + SDK client - client = deathbycaptcha.HttpClient("USER", "PASS") - captcha = client.decode(type=4, token_params={ - "googlekey": sitekey, "pageurl": url}, timeout=180) # CaptchaAI: API key + plain REST, no SDK + requests.post("https://ocr.captchaai.com/in.php", data={ + "key": KEY, "method": "userrecaptcha", + "googlekey": sitekey, "pageurl": url})
Drop the SDK dependency — submit a task and poll for the result over plain HTTP.
Supported CAPTCHA types
Two things developers reconsider
DeathByCaptcha is a veteran. Two things start to matter as you grow.
DeathByCaptcha built its reputation on classic image CAPTCHAs and still handles them well. But it doesn't list the full-page Cloudflare Challenge or BLS, and its per-solve billing grows with every solve. Here's what changes on CaptchaAI.
Why teams move
Five reasons developers switch from DeathByCaptcha
1. Types DeathByCaptcha doesn't list
The full-page Cloudflare Challenge (cf_clearance cookie + user agent) and BLS CAPTCHA — neither appears in DeathByCaptcha's supported types.
2. API key, no SDK
An API key and plain REST calls replace the DeathByCaptcha client library and its username/password or auth-token login. One less dependency to ship.
3. One plan for every type
Threads cover reCAPTCHA, Turnstile, GeeTest v3, BLS and image CAPTCHAs alike, with no per-type rate card to track.
4. Lower cost at volume
Thread pricing with unlimited solves per thread. From about 5,200 reCAPTCHA v2 solves a month, BASIC ($15/month) costs less than paying DeathByCaptcha's $2.89 per 1,000, and the gap widens as volume grows.
5. Retries at no extra cost
Each thread includes unlimited solves, so a retry costs nothing extra and there is nothing to report. DeathByCaptcha refunds an incorrect solve only when your software reports it within 60 minutes.
Trial to test first
Validate CaptchaAI on your own targets with a 3-day trial (5 threads) or a free thread for 30 days.
Migration
Drop the SDK, keep the workflow
DeathByCaptcha steers integrations to its official client libraries, signed in with a username/password or auth token. CaptchaAI uses a plain REST endpoint and an API key — so migration mostly means removing a dependency and parsing a pipe-delimited response.
- Replace
HttpClient("user","pass")with your CaptchaAIkey client.decode(...)→POST in.php, then pollres.php?action=gettype=4(reCAPTCHA) →method=userrecaptcha- Parse the pipe-delimited REST response instead of the SDK's result object
import requests, time API_KEY = "YOUR_CAPTCHAAI_KEY" API_URL = "https://ocr.captchaai.com" def solve_recaptcha(sitekey, pageurl): # Submit (replaces client.decode) r = requests.post(f"{API_URL}/in.php", data={ "key": API_KEY, "method": "userrecaptcha", "googlekey": sitekey, "pageurl": pageurl, "json": 1, }) task_id = r.json()["request"] # Poll for the result (no SDK, no socket) for _ in range(60): time.sleep(5) res = requests.get(f"{API_URL}/res.php", params={ "key": API_KEY, "action": "get", "id": task_id, "json": 1, }).json() if res["request"] != "CAPCHA_NOT_READY": return res["request"] raise TimeoutError("Solve timeout") # Start a 3-day trial at captchaai.com/trial to get your API key
Side by side
CaptchaAI vs DeathByCaptcha
Capability coverage, as each service documents it — see the evidence note.
| Feature | CaptchaAI | DeathByCaptcha |
|---|---|---|
| reCAPTCHA v2 | ||
| reCAPTCHA v3 | ||
| reCAPTCHA Enterprise | Beta | |
| Cloudflare Turnstile | Beta | |
| Cloudflare Challenge (full page) | ||
| GeeTest | v3 | v3 / v4 |
| BLS CAPTCHA | ||
| Image / OCR types | 27,500+ | |
| Authentication | API key | Username / password or auth token |
| API style | REST (no SDK needed) | REST + Socket (SDK) |
| Billing model | Per thread (unlimited solves) | Per solve |
| Free way to test | Free thread (30 days) | Free credits on request |
Where DeathByCaptcha may fit: if you only solve classic image CAPTCHAs and already have an integration built on its SDK, you specifically need its socket API, or you need a type it lists that CaptchaAI doesn't solve (such as GeeTest v4 or Amazon WAF), staying put can be reasonable. For the full-page Cloudflare Challenge, BLS, and lower cost at scale, CaptchaAI is the stronger match.
Illustrative pipeline
What changes day to day
Representative example for a high-volume reCAPTCHA pipeline. Your numbers depend on target sites and proxy quality.
Before — DeathByCaptcha (SDK, per-solve)
After — CaptchaAI (REST, thread-based)
Pricing
Pay per thread. Unlimited solves.
A thread is one in-flight CAPTCHA. It frees up the moment it finishes — so you size by concurrency, not by solve count. No per-CAPTCHA fees, no type surcharges.
Larger plans — CORPORATE ($240/mo, 150 threads), ENTERPRISE ($300/mo, 200 threads), and VIP tiers up to 5,000 threads. See full pricing →
Where the gap widens at scale
| Monthly reCAPTCHA v2 volume | DeathByCaptcha (per-solve) | CaptchaAI plan | CaptchaAI cost | You save |
|---|---|---|---|---|
| 10,000 solves | ~$29 | BASIC (5 threads) | $15 | ~48% |
| 100,000 solves | ~$289 | BASIC (5 threads) | $15 | ~95% |
| 1,000,000 solves | ~$2,890 | ADVANCE (50 threads) | $90 | ~97% |
| 10,000,000 solves | ~$28,900 | 2× ENTERPRISE (400 threads) | $600 | ~98% |
Illustrative, using DeathByCaptcha's published reCAPTCHA v2 rate (~$2.89 / 1,000, deathbycaptcha.com/user-pay, accessed September 2026) against CaptchaAI plans sized to peak concurrency. The thread model wins because once threads are paid for, additional volume runs through them at zero marginal cost. Confirm live numbers on captchaai.com/#pricing-plans.
FAQ
Frequently Asked Questions
Yes. You replace the DeathByCaptcha client library and username/password auth with a CaptchaAI API key and plain REST calls to in.php / res.php. The workflow is the same (submit a task, poll for the result), and you remove the SDK dependency entirely.
For a single integration point it is usually quick — swap client.decode(...) for a POST to in.php, change type=4 to method=userrecaptcha, poll res.php, and parse the pipe-delimited response instead of the SDK's result object.
Yes. Every new account can start a 3-day trial with 5 threads — start it at captchaai.com/trial (then $15/month via PayPal unless you cancel) — or claim a free thread for 30 days. The free thread is a no-cost way to compare on your own targets before you move production traffic.
If you only solve classic image CAPTCHAs and already have a working integration on its SDK, or you specifically need its socket API, staying put can be reasonable. DeathByCaptcha's image/OCR has a long track record. Run CaptchaAI on a free thread or a 3-day trial and compare for your use case.
Above about 5,200 reCAPTCHA v2 solves a month, yes — DeathByCaptcha bills per solve (reCAPTCHA v2 around $2.89/1,000), while CaptchaAI bills per thread with unlimited solves. The thread model's advantage grows with volume. Compare your monthly solve count against a thread tier on the pricing page.
CaptchaAI covers the full-page Cloudflare Challenge (cf_clearance cookie) and BLS multi-image CAPTCHA, which DeathByCaptcha doesn't list. DeathByCaptcha does list reCAPTCHA v3/Enterprise, Turnstile and GeeTest v3/v4 (several in beta).
Need more help? Check CaptchaAI Help Center
Ready to switch? Test it first, then drop the SDK.
Start a 3-day trial, point your solver at ocr.captchaai.com,
and run a real solve over plain HTTP. Keep DeathByCaptcha alongside until you're confident.
Evidence & sources
CaptchaAI's capability coverage is from its published supported CAPTCHA types (api-docs). DeathByCaptcha's is from its own documentation (deathbycaptcha.com/api): supported types including reCAPTCHA v2/v3/Enterprise, Turnstile, GeeTest v3/v4 and Amazon WAF, several in beta, with no BLS or full-page Cloudflare Challenge; official client libraries and a socket API; and username/password or auth-token login. Its free test credits on request are from deathbycaptcha.com/faq, both accessed September 2026.
Cost examples use published CaptchaAI plans (captchaai.com/#pricing-plans) and DeathByCaptcha's published reCAPTCHA v2 rate (~$2.89 / 1,000), both accessed September 2026. Pricing and supported types change over time — confirm current numbers before relying on them. Solve times are representative, not guaranteed; results vary by target site and proxy quality.
