Blocked by Kasada and DataDome? One request gets you through.
Send us the page that blocked you. We send back the token that gets you in, in about five seconds. If it doesn't work, you don't pay.
Endpoint
POST /api/tasks
{
"target": "https://www.example.com/checkout",
"provider": "kasada",
"proxy": "http://user:[email protected]:8080"
}Where the 5.31s went
{
"task_id": "3f6a1c02…",
"status": "success",
"solution": {
"ct": "eyJhbGciOi…q7Vx",
"cd": "{\"workTime\":17…}",
"st": 1757322131,
"r": "1-B",
"version": "ips-2026.31",
"cookies": { "KP_UIDz": "…" }
},
"latency_ms": 5310
}Endpoint
POST /api/datadome/solve
{
"type": "interstitial",
"device_link": "https://geo.captcha-delivery.com/interstitial/?…",
"html": "<!doctype html>…"
}Where the 0.35s went
{
"status": "success",
"post_url": "https://geo.captcha-delivery.com/interstitial/",
"payload": "jspl=…&ddk=…",
"headers": { "content-type": "…", … },
"user_agent": "Mozilla/5.0 …"
}
# replay it from your session. the datadome cookie is yours.What we solve
Two of the hardest walls on the web. Pick what you need, pay per success.
One key works for every vendor, the price is the price you see here, and a solve that doesn't land costs nothing. There is no sales call behind any of it.
The wall in front of sneaker drops, ticketing and streaming logins. Send us the page that blocked you and we send back a working token in about five seconds. If it doesn't work, you don't pay.
| What you get | Typical time | Price |
|---|---|---|
|
We do all of it
Send the URL and a proxy. We fetch the page, run Kasada's script and hand you a token that works. about 5 seconds
|
about 5 seconds |
$2.00
per 1,000
|
|
You fetch, we sign
Already running your own browser-grade client? Send us the script and we return the one request you can't build. about 200 ms
|
about 200 ms |
$1.00
per 1,000
|
|
Proof-of-work, unlimited
Kasada wants a new proof on every request you make. We mint them for free, as many as you need. instant
|
instant |
Free
unlimited
|
We tell you when it is done, or you ask. Your call.
The "checking your device" page and the slider puzzle. You keep your own connection; we tell you exactly what to send so it waves you through.
| What you get | Typical time | Price |
|---|---|---|
|
The "checking your device" page
The screen most scrapers hit first. We return exactly what to post so your session sails through. about 350 ms
|
about 350 ms |
$3.00
per 1,000
|
|
The puzzle slider
We find the notch and drive a human-looking drag. Slower on purpose, because that's what passes. 2 to 4 seconds
|
2 to 4 seconds |
$3.00
per 1,000
|
|
Trust signals
The background data a real browser sends. Send it too and you'll see far fewer challenges in the first place. about 200 ms
|
about 200 ms |
$3.00
per 1,000
|
Answers in the same request. Nothing to poll.
Blocked by something we don't list? Tell us before you build anything. We'll say straight whether we can solve it, and when we can, it becomes a tab up there.
Tell us who's blocking you →Getting your result
Ask us, or let us tell you. Or let your AI agent do both.
Ask us
Check on a solve as often as every 100 ms. Checking is always free and never counts against your limits.
202 { "status": "processing" }
200 { "status": "success",
"solution": { … },
"latency_ms": 5240 }We tell you
Give us a URL and we call it the moment a solve lands, signed so you know it's us. If you're down, we retry for two hours.
Solvr-Event: task.completed
Solvr-Signature: t=1699…,v1=<hmac>
{ "task_id": "3f6a…", "status": "success", … }Your AI agent
Using Claude Code, Cursor or Codex? One command and your agent can solve a wall itself the moment it hits one, on the same key.
$ claude mcp add --transport http getsolvr \
https://app.getsolvr.io/mcp \
--header "X-API-Key: solv_live_…"Built by people who have been paged at 3am.
- up to 50 at once No rate limits. A cap that grows with you.
- A solve takes seconds, so "requests per minute" is the wrong measure. You are limited on how many run at the same time, and the cap rises automatically with what you spend over a rolling 30 days.
- check our work We show you our grade
- Every Kasada token comes back with the score the vendor gave it. Nobody else shows you that. Compare it with your own success rate and see for yourself.
- a reason, every time Failures tell you why
- When a solve fails you get a plain reason and a yes-or-no on whether to retry. Never a bare error code and a guess.
- never stored Your proxy stays yours
- Send a proxy with each request and the solve runs through it. We keep the host for debugging and throw the credentials away.
- retries for 2 hours Webhooks that survive your deploys
- If your endpoint is down we keep trying for two hours, and we stop on our own if it stays dead so a bad deploy never floods you.
- gone in 72 hours We do not keep your tokens
- A token is only valid for minutes anyway. We delete it from our side within 72 hours, because keeping it helps nobody.
Questions
Straight answers.
How fast is it, really?
A full Kasada solve takes about five seconds, because we fetch the real page through your proxy and run the real script. If you already run your own client and only need the signed piece, that comes back in about 200 milliseconds. DataDome device checks take a few hundred milliseconds; the puzzle slider takes two to four seconds because a human-speed drag is what passes.
What happens when it fails?
Nothing, to your balance. A failed solve is free. You get a plain reason back (their fingerprint check refused it, the site timed out, we were briefly full) and a yes-or-no on whether to try again.
Which sites does it work on?
Any site protected by Kasada or DataDome. Send us the page that blocked you; we do not keep a list of allowed targets. Blocked by something else? Tell us and we will say straight whether we can solve it.
Do I have to talk to sales?
No. Create an account, add from $5 by card or crypto, and your key works immediately. How many solves you can run at once grows with what you spend over a rolling 30 days; nobody has to approve it.