API reference
Task submission, results, balance and API-key deposit addresses with full request and response schemas.
Docs
Documentation
SurSolver is an HTTP API: you send a page URL with the parameters you read from that page, and you get back the token or cookies it expects. Everything here is written against the task and deposit APIs.
Start here
Three pages take you from an empty account to a solved captcha.
Guide
Quickstart
Send your first captcha task from curl, Playwright, Puppeteer, Selenium or a browser extension — five steps from an API key to a solved captcha.
GuideAuthentication
How clientKey authenticates every solver call, how API keys are created and rotated in the dashboard, and what each authentication failure code means.
GuideErrors
Every error code the SurSolver API can return, what each one means, which side caused it, and the exact step to take to recover from it.
Guides
The concepts behind the API: tasks, proxies, limits, billing and moving over from another provider.
Guide
Task lifecycle
What happens between createTask and getTaskResult — statuses, how long answers stay, failures and what a failed task costs.
GuideProxies
Which task types need a proxy, the proxy formats the API accepts, and how to keep exit IP and user agent consistent so solved tokens verify on your side.
GuideRate limits
Default per-minute limits on task submission and result polling, what a rate-limit refusal looks like, and how to back off without losing throughput.
GuideBilling & packages
How a task is charged against your balance, how subscription packages are spent, what happens when a solve fails, and where refunds and credits come from.
GuideMigration
Moving an existing 2Captcha or Anti-Captcha integration to SurSolver: the fields that map one-to-one, the ones that change, and a checklist to test against.
GuideExamples
Runnable curl, Python, Node.js and Playwright examples for createTask, getTaskResult and getBalance that you can paste straight into your own code.
llms.txt
The same documentation as plain markdown for tools and agents: llms.txt lists the pages, llms-full.txt joins them, and every page has a.md twin. The OpenAPI file is at /openapi.json.