Guides / Requests vs results
Requests vs results: don’t mix billing units
ScraperAPI-style vendors often bill per request or credit. Oxylabs-style Web Scraper APIs often bill per successful result. Those numbers are not interchangeable without your own success-rate math.
What each unit means
- Request / credit — you pay when you call the API (or spend a credit), even if the page is empty, blocked, or partially useful. Some plans add multipliers for JS render or premium proxies.
- Successful result / record — you pay for returned entities that count as success under the vendor’s rules (often 2xx/4xx content). Failed system attempts may not bill the same way.
Why Scrapemarket splits families
Our estimator only ranks plans inside one unit family at a time (for example “successful results” vs “requests or credits”). Mixing them in a single cheapest-first list would look precise and be wrong.
If you know you need ~1,000,000 HTML pages and 80% succeed, that is ~800,000 results for a result-billed vendor — not 1,000,000 requests automatically.
Quick conversion sketch
Rough bridge: results ≈ requests × success rate. Then run the cost check twice — once in each family — and compare the two verdicts with that conversion in mind.
Also watch JS render multipliers and concurrency caps on the plan chips; they change effective cost even when the headline $/1k looks fine.