Guides / Estimate cost
How to estimate scraper API cost
A practical workflow using Scrapemarket’s public list-price estimator — so you leave with a plan shortlist, not a gut feel.
1. Measure monthly volume in the right units
Count what the vendor will bill: requests/credits or successful results/records. Use a week of production-like traffic and multiply by ~4.3 for a month, or pick a known catalog size × refresh cadence.
2. Pick the matching unit family
On the cost check, choose “Successful results” or “Requests or credits”. If you are unsure, read requests vs results first.
3. Read the verdict, then the caveats
The top card is the cheapest public-list estimate for that volume. Check chips for success-only billing, JS multipliers, concurrency, and geo notes. “Needs overage” means included volume is not enough — the estimate already tries to add published overage when we have a per-1k rate.
4. Stress-test at 100k · 1M · 5M
Provider pages show fixed scenarios so you can see whether a cheap Micro-style plan collapses at higher volume. Pair pages do the same side-by-side for two vendors.
5. Confirm on the vendor page
Scrapemarket uses public list prices only. Enterprise discounts, custom SLAs, and unpublished SKUs will differ. Use the CTA to open current pricing, then negotiate if you are past list tiers.