Skip to content
NexCaptcha

Products

Two ways past a challenge. Same engine underneath.

Either we fetch the page for you and hand back the response, or we solve the challenge and hand back the token. The worker pool, the rate card and the billing rules are identical — pick the interface that fits your code, not your budget.

Automation API

Send your request through the gateway, get the page back.

You get back

The target page's actual response

Pick this one when

  • The whole page is behind an interstitial and the only thing you want out of it is the HTML.
  • Your crawler is plain HTTP, and reproducing a TLS fingerprint, a cookie jar and a matching user agent well enough for a token to be accepted is work you would rather not own.
  • You are walking many pages behind one challenge, and x-nc-session carries the cleared state across them at no extra charge.
  • You drive Playwright, Puppeteer or Selenium and want the shield handled underneath the browser, through the upstream-proxy mode.
Automation API

Captcha Solving API

createTask, read the token, submit it with your own request.

You get back

A token you submit yourself

Pick this one when

  • The captcha sits inside a form you are submitting with your own session, and the POST has to come from your own IP.
  • You already load the page fine and only one widget is in the way — reCAPTCHA, GeeTest, an image field, a slider.
  • Something other than your scraper owns the HTTP call: a mobile client, a worker queue, an internal service that just needs the token string.
  • You are migrating off another solver and want the createTask/getTaskResult calls to keep working with the base URL changed.
Captcha Solving API

Which one fitsThe full rate card

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.

Get your API keyTalk to an engineer