The real cost of solving reCAPTCHA at scale

If you automate anything on the public web for long enough, reCAPTCHA is the wall you hit most. It's on far more sites than Turnstile, hCaptcha, or the enterprise bot vendors combined. So when you wire in a solving service, the interesting question usually isn't "can it solve reCAPTCHA" (most can). It's what does it cost when you're doing this 100,000 times a month — or 10 million?

That's where the pricing model matters more than the per-solve price.

Two ways solvers bill you

1. Per-1,000 solves (usage-based). 2Captcha, Anti-Captcha, CapSolver, CapMonster — most of the market — charge per solve, quoted per 1,000 (~$1–$3 for reCAPTCHA). Your bill scales linearly with volume. Double the traffic, double the cost. Forever.

2. Thread-based (concurrency-based). A "thread" is one concurrent in-flight solve. You buy N threads and get unlimited solves per thread per month. Cost scales with peak concurrency, not total volume — so once sized, pushing more solves through is free.

The math

reCAPTCHA v2 at ~$2 per 1,000 vs thread-based tiers (illustrative — check current pricing):

| Monthly solves | Per-1,000 (~$2/1k) | Thread plan | Thread cost | Effective per-1k |

|---|---|---|---|---|

| 10,000 | ~$20 | 5 threads | ~$15 | ~$1.50 |

| 100,000 | ~$200 | 5 threads | ~$15 | ~$0.15 |

| 1,000,000 | ~$2,000 | 50 threads | ~$90 | ~$0.09 |

| 10,000,000 | ~$20,000 | 200 threads | ~$300 | ~$0.015 |

The usage column grows in a straight line. The thread column barely moves. At a million/month the effective per-1,000 is single-digit cents; at ten million it's a rounding error.

When each wins

• Low/bursty volume → usage-based (or a free tier). A few thousand a month with idle gaps? Pay per solve; you're not paying for concurrency you don't use.

• Sustained/high volume → thread-based. Solving continuously? Flat per-thread wins, and the gap widens the more you push.

The one ask of thread-based: size threads to peak concurrency, not total volume. Watch your live concurrency for a day, buy ~that many, done.

The token flow (so this isn't just pricing)

reCAPTCHA v2/v3 is the same three steps regardless of vendor — and on a 2Captcha-compatible API it's identical calls:

import requests, time

API_KEY = "YOUR_KEY"

BASE = "https://ocr.captchaai.com"   # 2Captcha-compatible

r = requests.get(f"{BASE}/in.php", params={

    "key": API_KEY, "method": "userrecaptcha",

    "googlekey": "SITE_KEY", "pageurl": "https://target.example/login"})

task_id = r.text.split("|")[1]

while True:

    res = requests.get(f"{BASE}/res.php", params={"key": API_KEY, "action": "get", "id": task_id})

    if res.text == "CAPCHA_NOT_READY": time.sleep(5); continue

    token = res.text.split("|")[1]; break

# inject token into g-recaptcha-response, submit the form

For v3 the same flow returns a token, but v3 returns a score driven by the session's reputation, not a puzzle — a separate rabbit hole; the cost model is the same either way.

The takeaway

For reCAPTCHA, don't ask the headline per-1,000 rate — ask what your bill looks like at 10× your volume. Usage-based 10×'s with you; thread-based is roughly flat. Size threads to peak concurrency, run the math on your real volume, and pick the model that matches your curve.