Buy credits.
Or reserve throughput.

It's prepaid. Buy credits up front; each successful live solve on a credit-metered key spends one credit. Or buy a fixed-duration pass and attach keys to its shared throughput pool, with no per-solve credit charge. Sandbox requests are simulated and never billed. Neither meter creates a bill in arrears.

For a credit-metered live solve, one credit is spent when a successful provider result is saved: a Turnstile token or a WAF clearance payload. Failed provider results are not billed, and internal retries are not separate purchases. An HTTP timeout does not cancel queued work; that solve can still finish and be billed later. A saved result does not guarantee acceptance by the target, which can perform additional session and security checks.

Each prepaid pack has a fixed total price. Compare its full purchase amount and the rate per 1,000 credits shown in the catalog above. There are no marginal brackets. Buy any combination of whole packs; unused credits stay in your balance. Checkout confirms the current catalog price.

Our comparison pages show dated, sourced pack and per-solve prices. Compare the full purchase amount as well as the unit rate. SolveGate specializes in Turnstile and Cloudflare WAF; broader services may also support reCAPTCHA, hCaptcha and image captchas.

No. Prepaid credits don't expire. Buy the packs you need and spend them down at your own pace; your balance and credit usage are available in the dashboard.

Yes. Set a monthly spend cap yourself in the dashboard (Settings → Usage & limits), up to your tier's ceiling. Once your spend in the month hits it the API returns 402 instead of solving, so a runaway job can't drain your balance unexpectedly. You can also give an individual API key its own monthly budget.

Limits only — rate limit, how many active API keys you can hold, and the ceiling on your self-set spend cap. The per-credit price, the solver, and coverage are identical on every tier. You move up automatically as your lifetime purchased credits cross each tier's threshold; you're never moved down.

Both. Pay by card through Stripe or in crypto through Cryptomus; either way credits land in your balance once the payment clears. Refunds reverse the corresponding credits from your balance.

A hard 429 with a Retry-After header telling you exactly how long to wait. Nothing queues, nothing is billed, and nothing silently falls back to your credit balance. Every key attached to the same pass draws from one bucket — two keys on a 20/s pass share 20/s between them, they don't get 20/s each.

It's a hard stop: any key still attached returns 402 pass_expired instead of solving. Passes never auto-renew — we don't charge you for a window you didn't buy. We email you three days out, one day out, and on the day it ends, each with a renew link, and the dashboard carries the countdown. You can also move the key back to credit metering at any point.

Yes — metering is per API key, not per workspace. Point your heavy production key at a pass and leave CI, staging and one-off scripts on credits. You can hold several passes at once and split keys across them. Your credit balance isn't frozen or expired by owning a pass; it just sits there for whatever isn't attached.