Captcha solvers: proxy guides

A captcha solving service returns a token. Many sites tie that token to the IP address that asked for it, so the service has to work through the same proxy as your own request. These guides show how each service takes a proxy.

• 2Captcha

  2Captcha is a long-running captcha solving service with a simple HTTP API. Its newer API takes a task as JSON, and a task can carry your own proxy.

• Anti-Captcha

  Anti-Captcha is one of the oldest captcha solving services. Its JSON API has two versions of most tasks: a proxyless one, and one that works through a proxy you supply.

• CapSolver

  CapSolver is an automated captcha solving service with a JSON API. Tasks that need your IP address take the proxy as a single string.

• CapMonster Cloud

  CapMonster Cloud is the hosted captcha solving service from ZennoLab. Its API follows the same task format as Anti-Captcha, so code written for one usually works with the other.

• DeathByCaptcha

  DeathByCaptcha is one of the older captcha solving services, with an HTTP API and client libraries for the common languages.

• CaptchaAI

  CaptchaAI is an automated captcha solving service whose API copies the 2Captcha request format, so tools with 2Captcha support can be pointed at it.

• NopeCHA

  NopeCHA solves captchas with a browser extension and with an API. The extension works inside your browser; the API's token requests can take a proxy.

• NextCaptcha

  NextCaptcha is a captcha solving API that follows the task format made common by Anti-Captcha, with proxyless tasks and tasks that use your proxy.

• Why Captcha Tokens Fail: The IP Address Mismatch

  A solved captcha token can still be rejected when it was solved from one IP address and submitted from another. Why that happens and how to avoid it.

• Captcha Solving Services and How They Use Proxies

  The main captcha solving services, how each one accepts your own proxy, and when a task needs one at all. With a setup guide for every service listed.

All categories