Migrate your solver without a rewrite
Move from Solverify, NSLSolver, CapSolver, 2Captcha, Anti-Captcha, CapMonster, NextCaptcha, EzCaptcha, NopeCHA, or DeathByCaptcha by changing the API URL and API key.
Two changes
- Point the API base URL at https://api.xsolve.me
- Replace the provider key with your Xsolve API key
Endpoint map
Full field-level examples live in the migration docs.
| Client style | Old path | Xsolve URL | Auth |
|---|---|---|---|
| Solverify | /createTask | https://api.xsolve.me/createTask | clientKey in JSON |
| Solverify | /getTaskResult | https://api.xsolve.me/getTaskResult | clientKey in JSON |
| NSLSolver | /solve | https://api.xsolve.me/solve | X-API-Key header |
| CapSolver | /createTask | https://api.xsolve.me/createTask | clientKey in JSON |
| CapSolver | /getTaskResult | https://api.xsolve.me/getTaskResult | clientKey in JSON |
| Anti-Captcha | /createTask | https://api.xsolve.me/createTask | clientKey in JSON |
| Anti-Captcha | /getTaskResult | https://api.xsolve.me/getTaskResult | clientKey in JSON |
| CapMonster | /createTask | https://api.xsolve.me/createTask | clientKey in JSON |
| CapMonster | /getTaskResult | https://api.xsolve.me/getTaskResult | clientKey in JSON |
| NextCaptcha | /createTask | https://api.xsolve.me/createTask | clientKey in JSON |
| NextCaptcha | /getTaskResult | https://api.xsolve.me/getTaskResult | clientKey in JSON |
| EzCaptcha | /createTask | https://api.xsolve.me/createTask | clientKey in JSON |
| EzCaptcha | /getTaskResult | https://api.xsolve.me/getTaskResult | clientKey in JSON |
| 2Captcha JSON | /createTask | https://api.xsolve.me/createTask | clientKey in JSON |
| 2Captcha JSON | /getTaskResult | https://api.xsolve.me/getTaskResult | clientKey in JSON |
| 2Captcha / CapMonster classic | /in.php | https://api.xsolve.me/in.php | key query or form field |
| 2Captcha / CapMonster classic | /res.php | https://api.xsolve.me/res.php | key query or form field |
| NopeCHA | /token | https://api.xsolve.me/token | key in JSON or query |
| NopeCHA balance | /status | https://api.xsolve.me/status | key in JSON or query |
| DeathByCaptcha | /api/captcha | https://api.xsolve.me/api/captcha | authtoken or password |
| DeathByCaptcha balance | /api/user | https://api.xsolve.me/api/user | authtoken or password |
| Shared JSON balance | /getBalance | https://api.xsolve.me/getBalance | clientKey in JSON |
| Native Xsolve | /task | https://api.xsolve.me/task | X-Api-Key header |
Turnstile task types
Sitekey tasks such as AntiTurnstileTaskProxyLess, TurnstileTaskProxyless, and CloudFlareTurnstileTask map to mode turnstile.
Challenge task types
Interstitial and Cloudflare challenge types, including AntiCloudflareTask and Turnstile tasks without a sitekey, map to mode iuam.
Frequently asked questions
How do I migrate to Xsolve from another CAPTCHA solver?
Set the API base URL to https://api.xsolve.me and replace the API key with your Xsolve key. Compatibility endpoints accept common CapSolver, 2Captcha, Anti-Captcha, and similar request shapes.
Do I need to rewrite my Turnstile or Cloudflare challenge client?
Usually no. Keep the existing createTask, in.php, token, or solve payload and point it at Xsolve. Native integrations can also use POST /task with mode turnstile or iuam.
Which Cloudflare task types does Xsolve accept?
Turnstile sitekey tasks map to mode turnstile. Cloudflare challenge and interstitial tasks without a sitekey map to mode iuam.