FAQ
Frequently Asked Questions
Yes — every new account gets a free trial so you can verify integration and CAPTCHA coverage before paying. Open a ticket at ticket.captchaai.com and our team will activate trial threads on your account.
We run a 99.9% uptime SLA across all regions, with auto-failover and 24/7 monitoring so your captcha solving stays consistent.
You can subscribe via Subscription Payment with PayPal — auto-renewal is supported. Need a different option? Open a ticket and we will arrange it.
Yes. Contact us via ticket with your preferred payment option — we cover crypto, regional wallets, bank transfer and more on request.
Yes. Our support team helps you wire CaptchaAI into your stack — Python, Node.js, Selenium, Playwright, Puppeteer, scrapers, automation bots, and browser extensions. Open a ticket or browse the help center for ready-made guides.
A thread is one simultaneous CAPTCHA solve. The BASIC plan includes 5 threads, STANDARD 15, ADVANCE 50, PREMIUM 100, CORPORATE 150, ENTERPRISE 200 — and VIP plans go up to 5,000. Pick the plan that matches your peak concurrent traffic.
No daily limits. Each plan gives you a fixed number of concurrent threads and unlimited solves per thread. As long as your concurrent requests stay within your thread count, you can keep solving CAPTCHAs around the clock.
Requests over your active thread count are rejected with ERROR_NO_SLOT_AVAILABLE until a slot frees up. You can upgrade to a higher plan or add a second plan to your account at any time. Full error reference.
Yes. Subscribe to an additional plan and the system sums all active plans on your account — your usable threads become the total of every active subscription. No need to cancel your current plan. See plans.
reCAPTCHA Invisible verifies users in the background without requiring checkbox interaction, triggering challenges only when risk is detected.
→ Read Full Guide: How reCAPTCHA Invisible Works and How to Solve It
You can solve Invisible reCAPTCHA v2 by submitting the sitekey and page URL through API and retrieving a valid verification token.
→ Read Full Guide: How to Solve reCAPTCHA Invisible Using API
Failures may occur due to incorrect parameters, domain mismatch, or Enterprise configuration conflicts.
→ Read Full Guide: Common reCAPTCHA Invisible Errors and Fixes
Invisible reCAPTCHA v2 runs without visible checkbox interaction but follows similar verification logic to v2.
→ Read Full Guide: reCAPTCHA v2 vs Invisible reCAPTCHA Explained
You can solve reCAPTCHA v2 by submitting the sitekey and page URL to the API and retrieving a valid verification token.
→ Read Full Guide: How to Solve reCAPTCHA v2 Using API (Step-by-Step)
Web scraping workflows can integrate automated token generation to bypass reCAPTCHA v2 challenges efficiently.
→ Read Full Guide: How to Handle reCAPTCHA v2 in Web Scraping Workflows
Enterprise implementations require specific configuration parameters such as enterprise mode in the API request.
→ Read Full Guide: How to Identify reCAPTCHA Version (v2 vs Enterprise)
Failures may occur due to incorrect sitekey, invalid parameters, or mismatch between standard and Enterprise configuration.
→ Read Full Guide: Common reCAPTCHA v2 Solving Errors and Fixes
High reCAPTCHA v3 scores depend on correct action parameters, stable request behavior, and proper token generation.
→ Read Full Guide: How to Get High Human Score on reCAPTCHA v3
Low scores are triggered by risk signals detected during behavioral evaluation and request validation.
The action parameter defines the context of verification and directly impacts risk scoring logic.
Submit the sitekey, page URL, and action parameter to generate a valid score-based verification token.
→ Read Full Guide: How to Solve reCAPTCHA v3 Automatically Using API
reCAPTCHA v2 Enterprise includes advanced risk analytics and enhanced behavioral evaluation compared to the standard version.
→ Read Full Guide: reCAPTCHA Enterprise vs Standard — Complete Guide
Enterprise solving requires enabling enterprise mode and submitting correct parameters to generate a valid enterprise token.
→ Read Full Guide: How to Solve reCAPTCHA v2 Enterprise Using API
Enterprise implementations require enterprise-specific configuration in the solving request.
→ Read Full Guide: How to Identify reCAPTCHA Enterprise Implementation
Verification failures often occur due to missing enterprise mode or incorrect configuration parameters.
→ Read Full Guide: Common reCAPTCHA v2 Enterprise Errors and Fixes
No. Enterprise configurations require the Enterprise solver to generate compatible tokens.
→ Read Full Guide: Standard vs Enterprise reCAPTCHA v2 Solver Differences
Use enterprise mode in the API request to generate enterprise-compatible verification tokens.
→ Read Full Guide: How to Solve reCAPTCHA v3 Enterprise Using API
Enterprise uses enhanced behavioral analytics and adaptive risk modeling for score evaluation.
→ Read Full Guide: How reCAPTCHA v3 Enterprise Risk Scoring Works
Enterprise adds advanced security analytics and enterprise-level configuration requirements.
→ Read Full Guide: reCAPTCHA v3 Enterprise vs Standard Comparison
No. Enterprise implementations require enterprise configuration for successful token validation.
→ Read Full Guide: Standard vs Enterprise reCAPTCHA v3 Solving Guide
Image captcha solving uses OCR-based recognition to extract text or identify required objects from captcha images.
Submit the captcha image to the API and retrieve the recognized result programmatically.
Solve Media is an image-based captcha that presents branded or text-based verification challenges.
OCR failures may occur due to distorted images, background noise, or uncommon captcha patterns.
A Grid Image CAPTCHA is a verification method where users must select specific images from a grid based on a given instruction (e.g., “select all traffic lights”). It is widely used across different CAPTCHA systems to distinguish humans from bots.
Grid Image captchas can be solved by identifying required objects within the image grid and submitting the correct selection programmatically.
→ Read Full Guide: How to Solve Grid Image CAPTCHA Automatically
Yes. Grid image selection is a core part of Google reCAPTCHA v2, typically triggered when additional verification is required after the initial checkbox or risk analysis.
Failures may occur due to dynamic image refresh, incorrect object recognition, or expired verification sessions.
→ Read Full Guide: Common Grid Image CAPTCHA Errors and Fixes
Cloudflare Challenge can be solved by sending required challenge parameters to the API to generate a valid cf_clearance.
→ Read Full Guide: How to Solve Cloudflare Challenge Using API
Cloudflare Challenge validates requests and requires clearance generation before granting access.
Failures may occur due to incorrect clearance usage, expired challenges, or missing request parameters.
Cloudflare Challenge is a protection layer that requires clearance validation, while Turnstile is a CAPTCHA alternative that returns a verification token.
→ Read Full Guide: Cloudflare Challenge vs Cloudflare Turnstile Explained
Cloudflare Turnstile can be solved by sending required challenge parameters to the API to generate a valid verification token.
→ Read Full Guide: How to Solve Cloudflare Turnstile Using API
Turnstile combines behavioral signals and lightweight challenges to validate users without traditional CAPTCHA images.
Failures may occur due to incorrect token handling, expired challenges, or missing request parameters.
→ Read Full Guide: Cloudflare Turnstile Errors and Troubleshooting
Cloudflare Turnstile is a token-based CAPTCHA alternative designed to minimize user interaction, while Cloudflare Challenge requires generating clearance (cf_clearance) to access protected pages.
→ Read Full Guide: Cloudflare Turnstile vs Cloudflare Challenge: Complete Comparison
GeeTest v3 uses a behavioral challenge-response system that validates user interaction before granting access.
Submit the required challenge parameters and retrieve the validation token programmatically.
Verification may fail due to incorrect challenge values or expired session tokens.
GeeTest relies more heavily on interactive behavioral puzzles compared to Google’s risk-scoring models.
BLS captcha typically uses grid-based image selection challenges to prevent automated submissions.
Automated solving can be achieved through grid recognition and token generation workflows.
Failures may occur due to dynamic image updates or incorrect grid response handling.
Yes. Although both may use grid-based selection, BLS captcha implementations differ in verification structure.
→ Read Full Guide: BLS CAPTCHA vs reCAPTCHA Grid — Comparison
Usually no. CaptchaAI integrates directly with most automation software via API or built-in support.
Absolutely. You get API access, documentation, emulator options and Chrome Extension if needed.
Yes. The CaptchaAI Chrome extension auto-solves reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstile and image CAPTCHAs in the background — connect your account key and it just works. Install from Chrome Web Store.
Install the CaptchaAI Chrome extension, connect your API key or account key, enable the supported CAPTCHA types you want to use,
and run it on supported CAPTCHA pages inside Chrome. Install Extension here
Yes. New users can open Account options inside the extension to claim free threads and test supported CAPTCHA solving flows before moving to a paid plan.
Install Extension here and claim your free Trial
The extension supports solving multiple CAPTCHA types, including reCAPTCHA flows, Cloudflare Turnstile, GeeTest v3, image CAPTCHA workflows,
grid image CAPTCHA, BLS CAPTCHA, and other supported browser-based CAPTCHA verification flows.
Yes. To use the CaptchaAI Chrome extension, you need to connect your CaptchaAI account using your API key or account key through the extension settings.
Copy Your API Key here
Yes. The extension includes per-type controls, so you can enable or disable solving CAPTCHA types based on your workflow and browser automation needs.
You can install the extension for free, but CAPTCHA solving requires an active CaptchaAI account with available threads or an active plan.
New users may also be able to claim free threads through the extension for testing.
Install CaptchaAI Extension here and claim your free threads for testing.
No. CaptchaAI uses the same in.php / res.php request and response format. You change the endpoint URL and your API key — the rest of your solve logic, status checks, and error handling keep working.
For API users it's usually a few minutes — swap the base URL and key. Wrapper-library users typically need no logic changes because the compatible format means the same method names and parameters.
Use it up. Point new projects at CaptchaAI and migrate existing ones as your 2Captcha credits run down. There's no forced cut-over.
Yes. Every new account gets a 3-day free trial with 5 threads — claim it here. Run CaptchaAI and 2Captcha in parallel on the same workload, compare solve times and success on your real targets, then cut over when you're satisfied — your remaining 2Captcha balance stays usable.
No. CaptchaAI returns the same status codes and error formats (including CAPCHA_NOT_READY while polling), so your existing handling carries over.
You pay for concurrent threads, and each thread does unlimited solves per month. For steady high-volume workloads that makes monthly cost predictable, since it scales with concurrency rather than total solve count. Compare your current monthly solve count against a thread tier on the pricing.
No — CaptchaAI uses REST query parameters (in.php / res.php) rather than Anti-Captcha's JSON createTask API. But the workflow is identical (submit a task, poll for the result), so migration is updating endpoints, mapping a few field names, and switching response parsing.
For a single integration point it's usually quick — convert the JSON task object to query parameters (type → method, websiteKey → googlekey, websiteURL → pageurl) and switch your response parsing. The submit-then-poll control flow stays the same.
Yes. Many developers run CaptchaAI as the primary solver and keep Anti-Captcha as a fallback. The integration patterns are similar enough that a simple try/catch wrapper handles failover.
Yes — and this is a difference from Anti-Captcha, which has no free trial. Every new CaptchaAI account gets a 3-day free trial with 5 threads — claim it here. Run both solvers in parallel on the same workload, compare on your real targets, then cut over when you're satisfied.
On standard reCAPTCHA, Anti-Captcha often returns faster best-case times (around 15–25s for reCAPTCHA v2). CaptchaAI prioritizes consistent solvatically at no extra charge. If raw best-case latency on standard types is your top priority, weigh that in your test.
CaptchaAI covers the full-page Cloudflare Challenge (returning a cf_clearance cookie), BLS multi-image CAPTCHA, and custom grid-select challenges. Anti-Captcha supports Turnstile only and has no BLS or grid equivalent. Anti-Captcha in turn adds GeeTest v4 support.
No — CaptchaAI uses REST query parameters (in.php / res.php) rather than CapMonster's JSON createTask API. But the workflow is identical (submit a task, poll for the result), so migration is updating endpoints, mapping a few field names, and switching response parsing.
No. CaptchaAI is a fully managed cloud service — there's no desktop app to install and no CPU or proxies to run yourself. You call the API and we operate the solving infrastructure.
Yes. Submit to CaptchaAI first and fall back to CapMonster on a timeout. The two use different API formats, so you keep separate integration code, but a simple try/catch wrapper handles failover.
Yes. Every new account gets a 3-day free trial with 5 threads — claim it here. Run CaptchaAI and CapMonster in parallel on the same workload, compare on your real targets, then cut over when you're satisfied.
It depends on volume. CapMonster's per-solve rate can be cheaper at low monthly volume (around 10K solves). Above roughly 50K solves/month the thread model is typically cheaper because each thread does unlimited solves. Compare your monthly solve count against a thread tier on the pricing page.
CaptchaAI covers the full-page Cloudflare Challenge (returning a cf_clearance cookie) and BLS multi-image CAPTCHA, plus a broad 27,500+ image/OCR set. CapMonster supports Turnstile tokens only and has no BLS equivalent. CapMonster in turn offers a desktop self-hosted build, built-in batch queuing, and GeeTest v4.
No. CaptchaAI uses its own REST in.php / res.php format rather than CapSolver's JSON createTask API. But the workflow is identical (submit a task, poll for the result), so migration is a small field mapping, not a rewrite.
For a single integration point it is usually quick — convert the JSON task object to query parameters (type → method, websiteKey → googlekey, websiteURL → pageurl) and switch your response parsing. The submit-then-poll control flow stays the same.
Yes. Set up CaptchaAI as a parallel solver, verify it on your real targets, then move traffic over. You can keep CapSolver running as a fallback during the transition.
Yes. Every new account gets a 3-day free trial with 5 threads — claim it at captchaai.com/trial. Run CaptchaAI and CapSolver in parallel on the same workload, compare solve times and success on your real targets, then cut over when you are satisfied.
CapSolver currently supports AWS WAF and DataDome challenges that CaptchaAI does not cover yet. If those are central to your workflow, weigh that before switching. CaptchaAI in turn covers BLS and grid-image types that CapSolver does not.
At higher volume, the thread model is structurally cheaper because each thread does unlimited solves — so cost is driven by peak concurrency, not total solve count. Compare your monthly solve count against a thread tier on the pricing page.
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 gets a 3-day free trial with 5 threads — claim it at captchaai.com/trial. DeathByCaptcha has no free trial, so this 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 trial and compare for your use case.
In published rates, yes — DeathByCaptcha bills per solve (reCAPTCHA v2 around $2.89/1,000) with a $6.90 minimum deposit, while CaptchaAI bills per thread with unlimited solves and a $1 minimum. The thread model's advantage grows with volume. Compare your monthly solve count against a thread tier on the pricing page.
CaptchaAI covers Cloudflare Turnstile and the full-page Challenge, reCAPTCHA Enterprise, GeeTest v3, BLS multi-image CAPTCHA, and a broad 27,500+ image/OCR set. DeathByCaptcha focuses on classic image CAPTCHAs and reCAPTCHA v2 and doesn't support these modern types.
Yes. You update the API call format from NextCaptcha's JSON createTask to CaptchaAI's REST in.php / res.php and switch response parsing. The workflow is identical (submit a task, poll for the result), so the migration is straightforward.
For a single integration point it is usually quick — convert the JSON task object to query parameters (type → method, websiteKey → googlekey, websiteURL → pageurl) and switch your response parsing. The submit-then-poll control flow stays the same.
Yes. Every new account gets a 3-day free trial with 5 threads — claim it at captchaai.com/trial. Run CaptchaAI and NextCaptcha in parallel on the same workload, compare on your real targets, then cut over when you are satisfied.
If you are starting a brand-new project that only needs reCAPTCHA or hCaptcha, or your monthly volume is low enough that NextCaptcha's per-solve rate works out cheaper, it can be a reasonable fit. NextCaptcha also offers GeeTest v4. Run both on a free trial and compare for your specific use case.
It depends on volume. NextCaptcha's per-solve rate can be cheaper at low monthly volume (around 10K solves). Above roughly 15K solves/month the thread model is typically cheaper because each thread does unlimited solves. Compare your monthly solve count against a thread tier on the pricing page.
CaptchaAI covers the full-page Cloudflare Challenge (returning a cf_clearance cookie), BLS multi-image CAPTCHA, and a broad 27,500+ image/OCR set where NextCaptcha's image coverage is limited. It also ships client SDKs for more languages.
Need more help? Check CaptchaAI Help Center
