ASP auto-escalation: you can't know the cost before the request completes
Scrapfly's ASP (Anti-Scraping Protection) system automatically upgrades your proxy pool mid-request when it detects anti-bot protection on the target site. A datacenter proxy request β priced at 1 credit β can silently become a 25-credit residential proxy request if ASP determines the site requires it. Add JavaScript rendering (+5 credits) and you're at 30 credits for what started as a 1-credit call. Scrapfly documents this behaviour and it's part of what makes their success rate exceptional. But the practical consequence is cost unpredictability: you cannot model monthly spend on protected-site workloads without running production traffic first. On a Discovery plan with 200,000 included credits, protected-site scrapes at ~30 credits each deliver only about 6,667 actual pages β a 30Γ gap from the headline number. Multiple Capterra reviews flag this directly: "Credit pricing is opaque β ASP mode costs 10-25x a basic request, so a scraping job that looks cheap can burn through credits fast."
ScrapeBadger's Stealth mode costs a flat 23 credits per request β JS rendering and anti-bot bypass bundled. The cost is the same whether the target uses Cloudflare, DataDome, or no protection at all. You know exactly what a batch of 10,000 requests will cost before you run it.