Clear challenges inside the scrape path, not with a second vendor
Captcha Solving API
Handle CAPTCHA and challenge walls inside BrowserSolver unlock and render lanes. Detect with AntiBot, then scrape on the mode that fits, without wiring a separate solver account or credential.
- Challenge detection before you burn unlock credits
- Hybrid unlock for allowlisted hardened domains
- One balance for fetch, render, and challenge paths
- Vendor guides under /bypass for Cloudflare and peers
Detect
first
Unlock
allowlist
Retry
bounded
1 key
end to end
CAPTCHA as a scrape mode
- Step 1
Detect
AntiBot names CAPTCHA vs JS vs rate-limit walls.
- Step 2
Choose a lane
Rendering for JS walls, WebUnlocker for allowlisted challenges.
- Step 3
Parse
Return HTML to the same extractor you already run.
Challenges belong in the scrape path
Separate CAPTCHA vendors create another credential, another bill, and another failure mode. BrowserSolver keeps challenge handling next to the HTML you actually need.
- AntiBot names CAPTCHA vs JS vs rate-limit walls
- WebUnlocker for allowlisted domains that need hybrid unlock
- Failed unlock attempts follow published billing rules
- Same API key and credit balance across BrowserSolver scrape modes
Fewer moving parts in production
Your workers call one API. We decide whether cheap HTTP, render, or unlock is enough for the URL. Built for production jobs that need predictable access before brittle parsing.
- Mode hints reduce trial-and-error spend
- Session continuity across multi-step challenges where supported
- Docs and cheatsheets for common vendor stacks
- Same API key and credit balance across BrowserSolver scrape modes
CAPTCHA as a scrape mode, not a side quest
Detect, choose a lane, get HTML back into the parser.
Detect
Know the challenge family first.
Unlock
Hybrid lane on allowlisted hosts.
Sessions
Keep progress across hops.
Allowlist
Production unlocks on approved domains.
Retries
Bounded attempts, clear failures.
Billing
One credit pool for the job.
Inline
No second solver contract
Detect
Know the challenge family first
Allowlist
Production unlocks on approved hosts
Fair retries
Exhausted unlock attempts follow docs
WAF unlock guides
Runbooks for clearing common WAF and bot vendors with BrowserSolver.
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Do you solve every CAPTCHA type worldwide?
Coverage depends on domain allowlists and vendor playbooks. Confirm support for production hosts before scaling.
Should I still buy a third-party solver?
Most BrowserSolver scrapes should stay on detect → render/unlock. Use an external solver only if a workflow explicitly requires tokens outside our path.
Is this the same as WebUnlocker?
WebUnlocker is the unlock mode you call on allowlisted domains. Captcha Solving is the right product when challenge friction is the main blocker, not general HTML extraction.
Where are vendor pages?
Start at /bypass/cloudflare and browse the other WAF guides linked from the bypass hub.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes