CaptchaAI
Your CAPTCHA Bill Should Not Move Every Time Traffic Does.
Per-solve billing ties your costs to a number you do not control. CaptchaAI prices by concurrent thread instead: every plan ships no per-CAPTCHA fee and no daily cap, with no per-CAPTCHA fee, no daily cap and no surcharge by challenge type. The work becomes sizing concurrency correctly — which is arithmetic you can actually do up front.
The meter you cannot see until the invoice arrives
Per-solve pricing looks cheap at pilot volume because the multiplier is small. It scales with the one variable you least control - how often the target site decides to challenge you. A defensive change on their side moves your bill without anything changing on yours.
- Cost tracks the target's behaviour, not your own volume
- A campaign spike becomes a finance conversation
- Surcharges by challenge type make forecasting worse
- Daily caps turn a busy day into a failed job
How to size threads to real work
Threads are concurrency, not throughput. Four steps to a number you can defend.
Measure peak concurrency, not daily totals
A thread is one CAPTCHA in flight. What matters is how many are in flight at the same instant at your busiest minute - not how many you solve in a day. Averages hide exactly the peak that causes queueing.
Factor in how long each type takes
Solve time decides how long a thread stays occupied. CaptchaAI publishes Image CAPTCHAs at under 0.5s and reCAPTCHA v2 at up to 60s - the same job count needs very different concurrency depending on which type you are hitting.
Match the tier to the shape of your load
The published tiers exist as sizing guidance: BASIC at $15/month gives 5 threads for up to roughly 100K reCAPTCHA v2 a month; ADVANCE at $90 gives 50 threads for 250K-1M; ENTERPRISE at $300 gives 200 threads for 7.5M-10M.
Leave headroom, then measure again
Size for the peak you actually observed plus room for growth, then re-check once real traffic runs. Under-provisioned threads do not fail - they queue, which shows up as latency long before it shows up as an error.
What CaptchaAI publishes about its pricing
Straight from the client's own pricing section - the checkable parts.
No per-CAPTCHA fee
Every published plan states no per-CAPTCHA fee and no daily cap. Once a thread is paid for, each CAPTCHA cleared on it is included.
No per-CAPTCHA fees, caps or type surcharges
The pricing section states no per-CAPTCHA fees, no daily caps and no surcharges by type - the three mechanisms that usually make a solver bill unpredictable.
Named tiers with named thread counts
BASIC $15 / 5 threads, ADVANCE $90 / 50 threads, ENTERPRISE $300 / 200 threads, with a full ladder of BASIC, STANDARD, ADVANCE, PREMIUM, CORPORATE, ENTERPRISE and VIP-1 to VIP-3 published on captchaai.com/pricing.
Effective rates are the vendor's own arithmetic
The 'from $0.09 / 1K' and 'from $0.030 / 1K' figures are published effective rates at the stated volumes, not a quoted unit price - they move with how fully you use a thread. Treat them as sizing guidance.
Three inputs decide your thread count
Concurrency is not a guess once you know which levers feed it. Peak simultaneous jobs, how long each type holds a thread, and how much headroom you want for growth.
- Peak simultaneous jobs, measured at the busiest minute
- Hold time per challenge type, from the published bands
- Headroom for growth so you are not resizing monthly
- Re-measure once real traffic has run for a week
Why this way
The practical case, in four lines.
A bill that does not track someone else's behaviour
Per-solve billing moves when the target site changes how often it challenges you. Thread pricing does not.
No surcharge for the hard types
The published plans apply no surcharge by CAPTCHA type, so a shift in your traffic mix does not change the price.
Sizing you can defend in a budget meeting
Peak concurrency is a measurable number, which makes the plan choice arithmetic rather than a guess.
Room to grow without a renegotiation
The published ladder runs from 5 threads to 200 and beyond, so scaling is a tier change.
Before you pick a tier
What exactly is a thread?
One CAPTCHA in flight. Five threads means five solves can be in progress at the same moment; a sixth request waits for a slot. It is a concurrency limit, not a quota.
Do I get charged for failed solves?
The published model is per thread per month with no per-CAPTCHA fee and no daily cap, so there is no per-solve charge to incur on a failure. Check the current terms for the specifics of unsolvable responses.
How do I know if I need more threads?
Watch latency, not errors. Under-provisioned concurrency queues work, so the first symptom is jobs taking longer end to end while individual solves stay within their normal times.
Which plan should I start on?
CaptchaAI's own guidance maps BASIC to roughly 100K reCAPTCHA v2 a month, ADVANCE to 250K-1M and ENTERPRISE to 7.5M-10M. Start from your measured peak concurrency and treat those volumes as a sanity check.
Is there a free trial?
The site advertises free credits on signup with no credit card required, and mentions a free trial available via support. Confirm the current offer on the site.
Not sure how many threads you need?
Predictable billing, no per-solve fee
Buy the concurrency you measured, then stop watching the meter.