A single endpoint for every captcha - reCAPTCHA, AWS WAF, GeeTest and CaptchaFox. Sub-second latency, pay only for successful solves.
v2, v3 and Enterprise - checkbox, invisible and score-based.
Token and interactive AWS WAF challenges, desktop and mobile.
Slide, click and intelligent GeeTest challenges.
Interactive CaptchaFox proof challenges.
Cloudflare Turnstile non-interactive challenges.
What makes it hard: v3 runs invisibly and returns a 0.0-1.0 score instead of a pass/fail widget - there's nothing to click, so click-farms and generic proxy rotation do nothing. The site never shows a challenge, it just silently drops low scorers at the form handler. Enterprise sites layer stricter risk assessments on top.
How CapBypass solves it: We generate high-score tokens (typically 0.7-0.9) rather than guessing a threshold, by matching the pageAction from the target's own grecaptcha.execute() call so the token looks native to that specific flow. Both proxy and proxyless modes are supported, with a dedicated task type for Enterprise assessments.
Full reCAPTCHA solver docs →What makes it hard: A hybrid proof-of-work and interactive visual-grid challenge, driven by an encrypted key/iv/context blob (window.gokuProps) and two different scripts - challenge.js for basic page access, jsapi.js for signup and checkout - that have to match the action or you get rejected. Native mobile apps run an entirely separate on-device SDK flow.
How CapBypass solves it: We auto-detect gokuProps and the right script from just a websiteURL, or take manual key/iv/context/challenge.js parameters when you want full control. The solver returns the aws-waf-token cookie ready to attach - plus a dedicated mobile task type that mints tokens straight from the real AWS WAF mobile SDK, no URL or proxy required.
Full AWS WAF solver docs →What makes it hard: Nine different v4 interaction types (slide, icon, svg_icon, nine, word, phrase, space, pencil, voice) plus the older v3 fullpage slide puzzle, and the page never tells you upfront which one it's about to serve.
How CapBypass solves it: One task type auto-detects the variant and routes to the matching solver - v3 via gt + challenge, v4 via captchaId alone - and hands back the validated seccode payload. You never set a risk_type.
Full GeeTest solver docs →What makes it hard: A GDPR-first European proof challenge (slide, one-click or audio) layered with proof-of-work and behavioral signals, plus a handful of high-volume properties (mail.com, gmx.com, web.de) that route through a dedicated CaptchaFox host separate from the main flow.
How CapBypass solves it: We solve it over a pure-HTTP path, no browser required, and the dedicated-host routing for United Internet properties is handled automatically. Send the page URL and the sk_... site key - that's the whole request.
Full CaptchaFox solver docs →What makes it hard: No visible interaction at all - it profiles the browser and session in the background, so there's nothing to click and no image to classify. It's built specifically to catch the automation signals scrapers usually leak.
How CapBypass solves it: Shipping soon, using the same fingerprint-emulation approach that gets reCAPTCHA v3 to a 0.7-0.9 score, adapted to Turnstile's non-interactive flow.
Full Turnstile solver docs →Match what you're actually seeing on the target site against the list below - or read the breakdown above for how each solver clears it under the hood.