𝗧𝗵𝗲 𝗧𝗿𝘂𝘁𝗵 𝗔𝗯𝗼𝘂𝘁 𝗦𝗰𝗿𝗮𝗽𝗶𝗻𝗴 𝗔𝗣𝗜 𝗣𝗿𝗶𝗰𝗶𝗻𝗴 You need to know how scraping API pricing works. A scraping job that seems cheap at first can get expensive later. The surprise is not the price of one request, but the number of billable attempts needed to finish one job.
- Per-request pricing charges for each URL fetch.
- Session-duration billing charges for time instead of page count.
- You pay for each attempt, not just successful ones.
When you scrape one page and get one response, the model is simple. But when you need to scrape many pages behind the same Cloudflare session, billing each page independently can waste the session state you already paid for.
You should track cost per successful extraction, not cost per request. This number includes blocks, retries, and parsing failures. Run a test against each provider you consider, and record:
- Number of attempted pages
- Number of pages with expected content
- Number of challenge or block pages
- Median and p95 latency
- Total billed units
- Cost per successful extraction
Use per-request billing when each page stands alone and protection is light. Use browser-session billing when you need to keep state across many pages. Before you commit, run a test and calculate cost per successful extraction. This will tell you more than the pricing table. Source: https://dev.to/anakin_writers/how-scraping-api-pricing-changes-once-you-need-browser-sessions-2nm7