01
ROUTING
Low-latency routing
Requests are assigned against live solver capacity to reduce queue time across supported challenge types.
CAPTCHA solvingbuilt for production.
One API for Turnstile, DataDome, OCR, and modern anti-bot challenges. Route tasks across active capacity, monitor every state, and scale without rebuilding your integration.
create-task.json
$ curl -X POST https://solver.solverify.net/createTask
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "turnstile",
"websiteURL": "https://example.com"
}
}
TASK ACCEPTED
taskId: 81c4...f207
STATUS: COMPLETED
solution.value: ready
99.9%
24h success rate
Live task records
20,655,092
Tasks solved
Last 24 hours
99.9%
Target uptime
Redundant routing
$0.10
Starting price
Per 1,000 tasks
Infrastructure
Built like a processing platform, not a black box.
Every request moves through observable task states, account limits, and health-aware solver capacity designed for sustained automation.
02
UPTIME
Resilient processing
Redundant nodes and health-aware failover keep task processing available when individual workers degrade.
03
API
One REST workflow
Use the same create-and-poll integration model across Turnstile, DataDome, OCR, and other modules.
04
SCALE
Burst-ready capacity
Thread controls let your account absorb parallel workloads without rebuilding your application architecture.
Integration model
Three states. One predictable workflow.
Your backend creates a task, stores its ID, and retrieves the completed result. Clear boundaries make credentials, retries, queue control, and observability easier to own.
Create securely
Send tasks from trusted backend code so API keys, target validation, and retry policy stay under your control.
Poll deliberately
Keep the returned task ID and poll with bounded backoff until the task reaches a terminal state.
Scale from signals
Use pending work, active threads, balance, and solve time together before increasing submission volume.
Usage pricing
Pay for completed work, not idle capacity.
Transparent per-1,000 pricing for every active solution. Start small, validate against your own workload, and scale when the results make sense.
Per 1K
OCR
$0.10/ 1,000
Usage-based billing
$0.0001 per request
Per 1KTurnstile
$0.10/ 1,000
Usage-based billing
$0.0001 per request
Per 1KAliyun
$0.20/ 1,000
Usage-based billing
$0.0002 per request
Per 1KInterstitial
$0.20/ 1,000
Usage-based billing
$0.0002 per request
Per 1KAkamai
$0.40/ 1,000
Usage-based billing
$0.0004 per request
Per 1K
Alix5sec
$0.40/ 1,000
Usage-based billing
$0.0004 per request
Per 1KAwswaf
$0.50/ 1,000
Usage-based billing
$0.0005 per request
Per 1KPerimeterX
$0.50/ 1,000
Usage-based billing
$0.0005 per request
Per 1KDatadome
$0.60/ 1,000
Usage-based billing
$0.0006 per request
Per 1KImperva
$0.80/ 1,000
Usage-based billing
$0.0008 per request
Pay Per 1K concurrency
Start with 20 threads. Deposits add more.
Pay Per 1K accounts include 20 concurrent threads. Every complete $30 deposited in the rolling 30-day window adds 40 threads, up to 500 total.
Separate from the Threaded PlanThe Threaded Plan is a dedicated subscription with unlimited solves. Deposit-derived Pay Per 1K threads do not reduce its 500-thread purchase allowance.
Open an account Your rolling 30-day deposits
$120
Move the slider to calculate the extra concurrency included with Pay Per 1K billing.
$0$120$240$360+
Included base
20 threads
Deposit bonus
+160 threads
Total concurrency
180 threads
Example: $120 deposited gives 20 included + 160 bonus = 180 concurrent Pay Per 1K threads. Only completed $30 buckets count.
Evaluation path
Verify the service before production traffic.
Inspect the public API surface, review live operational health, and test your own workloads before increasing volume.
STEP 01
Request trial credits
New users can request 500 free Turnstile solves to evaluate latency and solve quality.
Contact supportSTEP 02
Build from public docs
Use request fields, result schemas, error codes, and examples maintained with the API.
Read documentationSTEP 03
Check live operations
Review solve volume, average completion time, queue usage, and node load before scaling.
Open status pageUse cases
Infrastructure for legitimate automation workflows.
Use Solverify only where you have the authority to automate, monitor, process, or test the target system.
QA automation
Repeatable browser and CI workflows on systems you are authorized to test.
OCR pipelines
Convert image-heavy inputs into structured text for internal processing and review.
Service monitoring
Run measured verification checks with observable task states and predictable limits.
Security testing
Controlled infrastructure for legitimate, permissioned security evaluation workflows.
Questions
Frequently asked questions
Common questions about our infrastructure and billing.
Can I test the service before purchasing?
Yes, we offer test credits for new users to evaluate our performance. Please contact our support team via Telegram to request a trial balance.
Is the service stable?
Absolutely. We maintain high stability to ensure your automation pipelines run without interruption.
What payment methods do you accept?
We currently accept crypto deposits only. Deposits are handled automatically inside your dashboard, so you can fund your balance directly from your account without manual intervention.
What is a 'thread'?
A 'thread' represents one concurrent connection to our API. It determines how many CAPTCHAs you can solve simultaneously. For example, with 100 threads, you can submit 100 CAPTCHAs at the exact same moment. Higher thread limits allow for greater throughput and parallel processing.
What is the difference between Threaded and Per-Request pricing?
Threaded Plan
You rent a specific number of concurrent threads for a fixed monthly fee. This grants you unlimited solves for the duration of your subscription. You are only limited by how many requests you can process simultaneously.
Per-Request (Per K)
You pay for each 1,000 CAPTCHAs solved. This is ideal for fluctuating volume. Additionally, based on your monthly deposit volume, we can offer increased thread limits while keeping you on the per-request pricing model.
Are there any volume limits or fair usage policies?
No, our thread-based plans are truly unlimited in volume. You can process as many CAPTCHAs as you want, provided you stay within your plan's concurrent thread limit.
What happens if I exceed my thread limit?
If you exceed your concurrent thread limit, additional requests will be rejected immediately. We recommend implementing retry logic or upgrading your plan to handle higher concurrency.
API Response Example
{
"errorId": 1,
"errorCode": "ERROR_THREAD_LIMIT_EXCEEDED",
"errorDescription": "Subscription user exceeded allowed concurrent threads"
}Do I get extra threads for high deposit volumes?
Yes. Extra threads are calculated from your total deposits made during the last 30 days. For every $30 in that rolling 30-day window, you receive 40 additional threads, up to a maximum of 500 total threads.
How it works:
- A $60 total deposit across the last 30 days gives you +100 threads.
- A $300 total deposit across the last 30 days gives you +420 threads.
- Once your rolling 30-day deposits reach $360, you hit the standard maximum of 500 threads. Anything above that requires a custom plan.
Ready to evaluate?
Ship your first task with 500 trial solves.
Create an account, read the quickstart, and test the exact challenge types your integration needs.