Captcha keys and Firm credits

Use our solver on credits, or bring your own CapSolver or KagedCap key.

Ticketing sites put a challenge in front of the pages worth watching. Solving one costs a fraction of a penny, but it has to be paid for somehow. You have two ways to do that, and you can pick per monitor.

Option 1: Firm credits (nothing to set up)

Leave the solver set to Firm and we handle it. Credits are prepaid: 1,000 solves for £1.50, bought from the same card as your subscription. Every solve is recorded against the monitor that asked for it, so the credits page shows exactly where they went.

A typical monitor uses roughly two to three solves an hour.
If a solve fails, the credit is returned automatically. You pay for answers, not attempts.
At zero credits the affected monitors pause rather than fail silently, and the slot is kept. Top up and they resume.
Optional auto top-up buys another pack when you drop below a threshold you choose.

Option 2: your own provider key

If you already buy solves, paste your key and we use it directly. Those monitors never touch Firm credits and we never see your balance; you are billed by the provider as usual.

Not available on Ticketmaster UK yet. Ticketmaster UK accepts only the Firm solver at the moment — your own CapSolver key is not used here. We measured it on 13 September 2026: over five alternating rounds on the same event and the same exits, tokens from a CapSolver key were accepted 0 times out of 5 (the site issues the clearance and then refuses it at first use), and the Firm solver was accepted 5 out of 5. So the new-monitor page does not offer the choice for that platform. A key you add here is still worth having — it is used on every platform that does accept one, and we will turn the choice back on for Ticketmaster UK the day a vendor token clears again.

CapSolver

Sign up at capsolver.com and add funds (a few dollars is plenty to start).
Open the dashboard; the API key is on the front page, starting CAP-.
Paste it into Settings → Captcha keys and press Verify key. We call their balance endpoint, which proves the key works and spends nothing.

KagedCap

Buy access through their Discord, which is where keys are issued.
Copy the key from the dashboard they give you.
Paste it into Settings → Captcha keys and save.

What the Verify button actually does

It calls the provider's balance endpoint. That proves the key exists, that it is spelled right, and that the account has funds — and it spends nothing, because no solve is requested.

Only CapSolver has a balance check here. For the others the key is stored and used as it is, and the row says "stored, not verified" rather than claiming a green tick on no evidence. The first real proof for those is a monitor that clears the site; if the key is wrong the monitor stops with your captcha key or proxy settings were rejected rather than failing quietly.

Where a screenshot would go: the Captcha keys page with one row - Provider "CapSolver", Key shown as four bullets and the last four characters, State reading "verified 13 Sep", and Verify / Delete buttons.

Keys are encrypted at rest with a key that lives only on the server, never rendered back into a page after you save them, and redacted from logs. If you rotate a key at the provider, paste the new one here and the old one is overwritten, not archived.

Which should I choose?

Start on Firm credits. It is one less account to manage and the per-monitor accounting is clearer. Move to your own key if you already have a bulk deal, or if you want the solve spend on a different invoice — on a platform that accepts one. Ticketmaster UK does not at the moment (above), so those monitors are on Firm credits whatever keys you hold.

Common problems

"Key rejected" when I verify

Nine times out of ten it is a stray space at the start or end of the pasted value. Copy it again and re-paste.

The monitor says "paused: no credits"

Your Firm balance hit zero. Top up on the credits page and it starts again by itself. The slot was never released, so nothing needs rebuilding.

Solves work but the monitor still sees nothing

That is not a captcha problem. Check the proxies first: a blocked exit and a failed solve look similar from the outside, and the monitor's status card tells you which one it was.

← Proxies: formats and gateways What a slot is →

Something here wrong or missing? Tell us, and we will fix the page rather than just answer the message.