Pricing
Every number, on this page.
Prepaid credit, drawn down per delivered solve across Kasada and DataDome. No plan, no seats, no minimum, and no sales call before you’re allowed to know the price.
| 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.
POST /api/tasks
about 5 seconds
|
about 5 seconds |
$2.00
per 1,000 · $0.002 each
|
|
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.
POST /api/kasada/payload
about 200 ms
|
about 200 ms |
$1.00
per 1,000 · $0.001 each
|
|
Proof-of-work, unlimited
Kasada wants a new proof on every request you make. We mint them for free, as many as you need.
POST /api/kasada/cd
instant
|
instant |
Free
unlimited
|
| 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.
POST /api/datadome/solve · type=interstitial
about 350 ms
|
about 350 ms |
$3.00
per 1,000 · $0.003 each
|
|
The puzzle slider
We find the notch and drive a human-looking drag. Slower on purpose, because that's what passes.
POST /api/datadome/solve · type=slider
2 to 4 seconds
|
2 to 4 seconds |
$3.00
per 1,000 · $0.003 each
|
|
Trust signals
The background data a real browser sends. Send it too and you'll see far fewer challenges in the first place.
POST /api/datadome/solve · type=tags
about 200 ms
|
about 200 ms |
$3.00
per 1,000 · $0.003 each
|
What you actually pay for
You pay for strong-grade successes, and nothing else. A solve that fails never touches your balance. Not "charged and refunded": never charged, so there is nothing to chase and nothing to wait for.
We also tell you what "success" means, which nobody else here does.
Kasada scores every session; a score starting
1-B is a pass, and we send
that score back to you with every token. A weak score is thrown away before it
becomes a token. Check our word against your own results any time.
The proof-of-work is free on purpose. The protected site wants a fresh one on every single request, so ten thousand pages means ten thousand of them. We mint them at $0 per proof-of-work. Charging would be putting a price on doing it properly.
- A bundle was delivered
- kasada · full solve · we run the network
- $0.002
- A transform was returned
- kasada · you run the network
- $0.001
- A challenge was solved
- datadome · you run the network · no proxy needed
- $0.003–$0.003
- The solve failed
- nothing delivered
- $0.000
- It hit the 45s deadline
- nothing delivered
- $0.000
- Engine backpressure
- retry shortly
- $0.000
- The fingerprint was rejected
- nothing delivered
- $0.000
- Polling a task
- a read
- $0.000
- A webhook delivery
- our cost
- $0.000
- Reading your balance
- a read
- $0.000
- A proof-of-work (cd)
- microseconds of hashing
- $0.000
Balance
Credit and concurrency both follow spend.
Bigger top-ups carry more credit, and spending it raises how many solves you can hold in flight. Nobody has to approve either.
Bigger top-ups carry more credit.
Credited the moment the payment clears, and it spends exactly like the rest of your balance. Solve counts assume every solve succeeds. Failures never draw the balance down.
| Top up | Bonus | Credited | Solves |
|---|---|---|---|
| $5 | — | $5.00 | 2,500 |
| $50 | +5% | $52.50 | 26,250 |
| $100 | +10% | $110.00 | 55,000 |
| $250 | +15% | $287.50 | 143,750 |
| $500 | +20% | $600.00 | 300,000 |
cents cannot represent $0.002 without rounding it away or overcharging you 5x. we never used them.
Your limit is how many run at once.
Requests per minute is the wrong unit for something that takes five seconds. What matters is how many proxy sessions and how much solving capacity you hold simultaneously.
| Tier | Spend in 30d | In flight |
|---|---|---|
| Evaluating | $0 | 1 |
| Starter | any spend | 5 |
| Growth | $50+ | 10 |
| Scale | $250+ | 25 |
| Pro | $1,000+ | 50 |
matched on top-ups, rolling 30 days
- 30-day window The window rolls
- Spend ages out gradually on your own timeline. A calendar month would demote every customer to 1 concurrent at midnight on the 1st and throttle live workloads without warning.
- top-ups only Only real spend counts
- Top-ups move you up a tier. Promotional and granted credit does not, which is what stops a giveaway being farmed at everyone else’s expense.
- 50 in flight The top tier is reached by spending
- Not by booking a call. Move up the ladder and the new limit applies on your next submission.
Payment
Card or crypto.
$5 to $10,000 per top-up. The same bonus ladder applies whichever way you pay.
- Card
- Visa, Mastercard and Amex via Stripe. We never see your card details.
- Crypto
- BTC, ETH, USDT, USDC, LTC, SOL, BNB and TRX via Cryptomus. Same bonus tiers.
Questions
Asked before the first top-up.
What happens when a solve fails?
Nothing is charged and you get a typed error kind saying why. Retryable failures (a busy engine, proxy trouble) are released and reattempted automatically before you ever see them.
Does credit expire?
No. Balance sits there until you spend it. There is no monthly minimum and nothing lapses.
Which vendors are live?
Kasada and DataDome. Others are priced and plumbed in but gated off until the engine genuinely serves them. The API returns a clear "not available" rather than a confusing error.
Do I have to talk to sales?
No. The price is above, the docs are public, and the top tier of 50 concurrent is reached by spending rather than by booking a call.
Can I see where the money went?
Every charge, top-up and promotional credit writes an append-only ledger row. Read it back per month, per provider and per target in your dashboard, or export the raw solve log as CSV.