Pricing
Prepaid credit, charged per solve, in USD. No subscription, no minimum, no monthly fee. Prices are published here because a price you have to ask for is a price that varies by how much you look like you can pay.
| Type | Identifier | Per 1,000 | Per solve |
|---|---|---|---|
| reCAPTCHA v2 | recaptcha_v2 |
$0.80 | $0.000800 |
| reCAPTCHA v2 invisible | recaptcha_v2_invisible |
$0.80 | $0.000800 |
| Cloudflare Turnstile | turnstile |
$1.20 | $0.001200 |
| Image OCR | image_ocr |
$0.60 | $0.000600 |
Prices are per solve returned, not per task submitted. A task that returns no solution is not charged.
List price is not what a solve costs you
List price is not what a solve costs you. What it costs is list price divided by the share of tokens your target actually accepts, and no vendor — including this one — can tell you that number in advance. We measure it per target domain and show it to you. In our own 195-solve benchmark against a property we control, every token was accepted, so cost per accepted solve equalled list price exactly. That is a fact about an undefended target, not a promise about yours.
This is the distinction the whole product is organised around, so it is worth being plain about both halves of it. A token your target rejects has cost you the solve, a burned proxy, a flagged session and a raised risk score — and the industry's answer to that is a refund of roughly $0.0008, which is off by orders of magnitude. Vendors report accuracy by their own verdict, which is whether they produced a token, not whether it worked.
We verify tokens against the challenge provider and attribute the result to the target domain, so the number you see is measured rather than asserted. Below a minimum sample size it is reported as not yet determinable rather than as a figure with no support under it.
What is not supported, at any price
hCaptcha, DataDome, Kasada, PerimeterX / HUMAN, FunCaptcha / Arkose. These are named here rather than left off the list, because their absence is the kind of thing a prospect should learn from a page rather than from a failing job.
Paying
Credit is prepaid and drawn down per solve. The balance is held by the solving gateway itself, which is what debits it — so it is accurate at the moment of the solve rather than at the moment a billing system catches up.
Payment rails are not open for self-service signup yet. Until they are, write to support@legibl.com and we will arrange it. We would rather say that than show a checkout that takes your card and then cannot deliver.