Skip to content
getsolvr
Get an API key
Menu

Anti-bot vendor

Kasada live

Blocked by Kasada? Get through in about five seconds.

No puzzle, no traffic-light pictures — Kasada just refuses you, again and again, and never says why. Send us the page that blocked you and we send back what gets you in.

Create an account API reference
about five seconds $0.002 when it works · nothing when it doesn’t $5 minimum · no subscription proofs of work cost nothing
Request a vendor

What you send with every request

the user agent and cookies come back too · send the same ones

The token
You get this once, by solving the challenge. It’s good for many requests after that.
x-kpsdk-ct · one per session
The proof
A tiny mark on every single request. We mint a fresh one for free, as many as you need.
x-kpsdk-cd · one per request
The version
Which build of the script your token was made for. Kasada changes it often; we keep up.
x-kpsdk-v · follows the site

The arithmetic

One token. Ten thousand proofs.

This is the part that catches people. Solving the wall once gives you a token you can reuse — but Kasada wants a fresh proof on every request that carries it. Solve once and fire ten thousand requests with a single proof and every one bounces, which looks exactly like a solver that doesn’t work.

So a crawl of ten thousand pages is one solve and ten thousand proofs. We charge $0.002 for the solve and $0.00 for the proofs — as many as you like. The ceiling sits at 200/s per key, well above how anyone actually uses it. Charging for the proofs would be charging you for doing it right.

A crawl of Solves Proofs Cost
100 pages 1 100 $0.00
1,000 pages 1 1,000 $0.00
10,000 pages 10 10,000 $0.02
100,000 pages 100 100,000 $0.20

assumes one session per 1,000 pages · your rotation is yours to choose · the proofs column is free at every row

Endpoints

Three ways in. Pick one.

Which one you want comes down to how much you’d rather we handle. One key, one balance, and a solve that misses always costs nothing. For integrators: every field, header and failure mode is in the reference.

Kasada live

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 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
$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
$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
Free
unlimited

We tell you when it is done, or you ask. Your call.

  • POST /api/tasks $0.002 per solve

    The one most people want. Send us the address that blocked you and a proxy to use, and we hand back everything you need to get in. Wait for it however suits you — check back, or let us call you the moment it lands. Most of those five seconds is the site loading through your proxy, not us.

    reference →
  • POST /api/kasada/cd $0.00 per proof

    Kasada wants a fresh proof on every request. Once you hold a token, this mints them — no network, no browser, instant. Call it as often as you like, forever, free.

    reference →
  • POST /api/kasada/payload $0.001 per script

    Already running your own browser-grade client? Keep your own connections, sessions and proxies. Send us the script and we return the one piece you can’t build yourself.

    reference →

Worked

Solve once, then keep going.

The whole integration, both halves. One call to get through the wall, then one cheap call per request after it. field reference →

once · the solve $0.002 if it lands 
$ curl -X POST app.getsolvr.io/api/tasks \
    -H "X-API-Key: solv_live_…" \
    -d '{"target":"https://www.example.com/",
         "proxy":"http://user:pass@host:8000"}'

202 { "task_id": "3f6a…" }

$ curl app.getsolvr.io/api/tasks/3f6a…

200 {
  "status": "success",
  "solution": {
    "ct": "eyJ0IjoiZncifQ…",
    "st": 1699999999,
    "cd": { … },
    "r": "1-B",          // the grade, returned
    "version": "p-2.7.1",
    "user_agent": "Mozilla/5.0 …"
  }
}
then · every request after it $0.00 per proof 
# a fresh proof, free, for each request
$ curl -X POST app.getsolvr.io/api/kasada/cd \
    -H "X-API-Key: solv_live_…" \
    -d '{"ct":"eyJ0IjoiZncifQ…","st":1699999999}'

# then your own request, through the same proxy
$ curl https://www.example.com/api/thing \
    -H "x-kpsdk-ct: eyJ0IjoiZncifQ…" \
    -H "x-kpsdk-cd: <fresh proof>" \
    -H "x-kpsdk-v: p-2.7.1" \
    -A "<the user_agent we returned>"

Same proxy for both halves. A token is tied to the address that made it, works once, and lives only minutes — we delete it within 72h regardless. A token solved through one proxy and used through another is the most common reason a token that looks fine gets refused.

Diagnosis

Is it even Kasada?

Worth thirty seconds before you buy anything from anyone. The walls look alike from the outside — you are blocked and you do not know by what — but they do not answer alike. Kasada puts its own headers on the refusal.

thirty seconds 
$ curl -sI https://the-site-you-are-stuck-on/ \
    | grep -i 'kpsdk\|cf-ray\|akamai\|datadome'

# x-kpsdk-* on the response → this page is for you

No captcha and no interstitial is itself a signal. Kasada does not ask you to prove anything a human can see — it decides, and then it refuses.

The wall, and how to tell Is it us?
Kasada

403 or 429, no captcha, headers on the refusal itself

x-kpsdk-ct · x-kpsdk-cd · x-kpsdk-v
 Yes solve it here
Cloudflare

an interstitial or a challenge page you can see

server: cloudflare · cf-ray · cf-mitigated
 Not us
Akamai

a sensor script and a long-lived cookie

akamai-grn · x-akamai-transformed · _abck cookie
 Not us
DataDome

a captcha page served from their own domain

x-datadome · datadome cookie
 Not us

signatures observed directly · a site can sit behind more than one of these at once

then: is the host tuned?

If it is Kasada, the next question is whether we have tuned that host. Profiles are per host. One we have not seen comes back as a typed unsupported_target rather than a failed solve you paid for, and reporting it is how it gets tuned — routine work, and better than a generic profile doing worse than it needs to on a site somebody actually cares about.

Failures

When a solve doesn't land.

You get a plain reason, never a bare error and a shrug. None of these cost you anything — a failure is a failure, and it never touches your balance.

Every reason we can give →
  • Their check didn’t trust your address

    The session was graded as a bad fingerprint (burned IP). Retry with a fresh proxy session.

    bad_fingerprint
    Retry
  • The page took too long to load

    The solve exceeded the deadline. This is almost always a dead or slow proxy. Retry with a fresh proxy session.

    upstream_timeout
    Retry
  • The site turned the token down

    The target refused the solve. If this persists on this host, report it so the profile can be tuned.

    rejected
    Retry
  • We haven’t tuned this site yet

    That target is not supported yet. Report the host and it will be tuned.

    unsupported_target
    Don’t retry
  • We were briefly full

    The solver is at capacity. Retry shortly.

    busy
    Retry

the ones marked Retry are reattempted for you before you ever see them

Site by site

Kasada, site by site.

each one checked, with the date on the page

Questions

Kasada, asked and answered.

The questions people actually arrive with, including the two that are usually the reason something is not working.

What is Kasada?

A bot blocker that hides behind a site instead of showing you a captcha. When you arrive, a script quietly checks your browser and makes it do a little busywork; until the site sees proof that all of it ran, it just refuses you. There is nothing for a human to click, so you usually meet it as a wall of refusals rather than a puzzle.

What are x-kpsdk-ct and x-kpsdk-cd?

The two things a request has to carry. The first is the token you get once, by solving the challenge — proof a real browser ran. The second is a small proof worked out fresh for every request, from that token and the clock. One solve gives you one token, good for many requests; each request still needs its own new proof.

Is one token enough for a whole crawl?

No, and this is what trips people up. The token is only half of it — every request also needs its own fresh proof. Ten thousand pages is one solve and ten thousand proofs. We charge $0.002 for the solve and nothing at all for the proofs.

How long does a Kasada solve take?

About five to six seconds, because we load the real page through your proxy and run the real script. We give up at 45 seconds, and anything that hits that is free rather than billed. We publish the real number so you can set your own timeouts against the truth, not a brochure figure.

Does the token work from any IP?

No. A token is tied to the address that made it, works once, and lasts only minutes. Give us your proxy when you solve, then make your request through that same proxy. Solving on one address and using the token from another is the number-one reason a token that looks fine gets refused.

Kasada changed their script. Do I have to do anything?

No. Keeping up with their script is our job. We tell you which build each token was made for, so you can watch it change. If a new build lands before we have caught up for a site, you get a clear reason and no charge, rather than a token the site quietly refuses.

Kasada is a trademark of Kasada Pty Ltd, which is not affiliated with Solvr. The name is used here to identify the protection this service answers. For authorised testing of systems you own or may assess.

$5 is 2,500 solves and every proof you can call for.

Create an account