How CAPTCHA and anti-bot systems really work — and how to handle them in production.
Before you can submit a solver task you need three facts from the page: which challenge it serves, the siteke…
The integration demo works; production is where it breaks. The error taxonomy every handler needs, deadlines…
A retry costs three things: a solve, a thread-second, and a slice of your egress reputation. Seven retry mist…
Turnstile is a form widget that mints a short-lived cf-turnstile-response token, not the Cloudflare interstit…
Some challenges record the network a token was earned from; others have no network context at all. How to tel…
robots.txt is a published preference, not a fence. Rate limits are an engineering constraint. Terms of servic…
A solve rate that falls with no deploy on your side almost always means the target changed. How to tell a new…
The legacy in.php / res.php protocol is shared by several solvers, so switching providers is usually a host s…
Thread-based pricing sells concurrency, not solves. How to measure real peak concurrency, why average through…
A site decides you're a bot before it shows you anything. How IP and ASN reputation, TLS fingerprints, header…
Image grids, BLS numeric grids, reCAPTCHA v2/v3 and Enterprise, Cloudflare Turnstile and Challenge, Geetest v…
How the submit-and-poll pattern actually works: POST a task to in.php, poll res.php until CAPCHA_NOT_READY st…