What is anti-bot detection?

Anti-bot handling matters to a bill because a protected request can consume many more credits than the basic route. Some vendors require the buyer to select the mode, while others can escalate routing automatically. A forecast based only on ordinary pages can therefore undercount credits when the production target uses a protection-specific configuration. These are billing rules, not outcome measurements. (ScraperAPI credit rules, Scrapfly billing rules, and ZenRows pricing rules, checked 2026-07-26.)

ScraperAPI publishes ten credits per scrape for named Cloudflare, Turnstile, DataDome, and PerimeterX bypass modes. Its stealth mode costs thirty credits, while ultra-premium routing with rendering has a larger combined cost. The documentation does not define how every bypass, target, and parameter cost combines, so those interactions remain unknown. (ScraperAPI credit rules, checked 2026-07-26.)

ScrapeOps publishes three generic bypass levels at ten, twenty-five, and forty credits. It separately lists PerimeterX at twenty-five and DataDome at forty, while premium levels and JavaScript combinations use other totals. These are replacement or combination rules, not one add-on that can be applied blindly to every base request. (ScrapeOps request costs, checked 2026-07-26.)

ZenRows publishes a twenty-five-credit protected mode alongside one-credit basic, five-credit JavaScript, and ten-credit premium-proxy modes. The four Universal Scraper modes replace one another. Failed requests and internal retries are free, while HTTP 404 and 410 responses are billed as successful. (ZenRows pricing rules, checked 2026-07-26.)

Scrapfly’s Automatic Scraping Protection can dynamically upgrade the proxy pool, changing the base request cost. JavaScript and excess response bandwidth are additive, so an automatically upgraded request can also accumulate those meters. Its failure-protection billing has conditions and can be disabled when eligible failures exceed the published traffic threshold. (Scrapfly billing rules, checked 2026-07-26.)

Before signing up, identify the target’s actual challenge and match it to a documented mode. Check whether escalation is manual or automatic, how named bypasses combine with rendering and proxies, which statuses are billed, and whether the response exposes the chosen route and debit. Set a maximum acceptable per-request cost when the vendor permits it, and test each target class separately. (ScraperAPI credit rules, ScrapeOps request costs, ZenRows pricing rules, and Scrapfly billing rules, checked 2026-07-26.)