Developer guide

Scraping API cost at scale: estimate monthly credits for 500,000 requests

Most scraping API quotes fall apart at volume. The headline price per 1,000 requests is for the cheapest kind of request. The kind you actually send, a rendered page through a premium proxy, is often billed at a multiple. This guide estimates a monthly bill for 500,000 requests and shows where the estimate usually goes wrong.

4 min read

Step 1: count requests, not pages

  • Daily checks of 5,000 product pages: about 150,000 requests a month.
  • Hourly checks of 700 pages: about 500,000 requests a month (700 × 24 × 30 = 504,000).
  • Retries count only if your provider charges for them. Here, failed and blocked requests are free. A wait_for selector that never shows up still returns the page (200, wait_timed_out: true) and costs 1 credit.

Step 2: find the multiplier

On UnblockingAPI there is no multiplier. One successful request is one credit, with JavaScript rendering, premium proxies, country routing and retries included in every request.

Our comparison pages put a rendered, premium-proxy request at 25 credits on ScrapingBee and ScraperAPI. At that rate, 500,000 requests would use 12.5 million credits there. Check their current pricing before you decide.

Step 3: price the credits

PackBonusCreditsPer 1,000
€10 pack-10,000€1.00
€50 pack+5%52,500€0.95
€100 pack+10%110,000€0.91
€250 pack+15%287,500€0.87
€500 pack+20%600,000€0.83

Packs are one-time purchases, and the credits never expire. For 500,000 requests there are two routes:

  • One €500 pack. 600,000 credits at €0.83 per 1,000, so about 100,000 of headroom that carries over to next month.
  • A €250 pack plus two €100 packs. 507,500 credits for €450. Cheaper at exactly 500,000, but with almost no headroom.

Every account gets the same 25 concurrent requests and 30 days of logs, whichever packs you buy. Prices exclude VAT. Current prices are on the pricing page.

Step 4: leave headroom

  1. Traffic you did not plan for. Budget 20 to 30% above your estimate.
  2. Concurrency. If a run must finish in a fixed window, check that 25 concurrent requests is enough. If it is not, talk to us about higher concurrency and dedicated capacity.
  3. Difficult targets. Run a few hundred requests per target before you scale and measure the success rate yourself.

A worked example

A team watches 700 product pages and checks each one every hour.

  • Requests: 504,000 a month, so about 504,000 credits.
  • Credits: one €500 pack, 600,000 credits.
  • Cost per successful request: about €0.00083.
  • Headroom: about 96,000 credits, which carry over because pack credits never expire.

Try it on your own targets

New accounts get 500 free credits with no card. Send a few hundred requests to the sites you care about and multiply the credits used by your monthly volume. See pricing or read the docs.

Know your bill before you scale.

Test the fetching layer before building your parser. Start with 500 free credits and no credit card. See pricing for credit packs from €10.

One successful request is one credit. No multipliers for rendering, proxies or retries.

Related guidesBrowse all guides

How to scrape public property listing pages

Fetch JavaScript-rendered property listing pages with country-level routing and parse the returned HTML.

How to scrape e-commerce product pages and pricing data

Fetch public product pages through UnblockingAPI, parse pricing and product details from the returned HTML.

How to scrape JavaScript-rendered pages

Use real browser rendering to fetch pages that load content dynamically through client-side JavaScript.

How to scrape hundreds of websites every day without breaking your pipeline

Separate fetching from parsing, queue small jobs, validate content and work out monthly credits before you buy.

A ZenRows alternative: credit multipliers compared

Compare ZenRows and UnblockingAPI on published rates, with worked examples at three volumes and where ZenRows may be the better fit.

A Bright Data alternative with flat per-request pricing

Compare Bright Data Web Unlocker and UnblockingAPI on published rates, with worked examples and where Bright Data is the better fit.

Bulk domain rating checker: Ahrefs DR for hundreds of domains

Check Ahrefs Domain Rating, backlinks and linking websites for a list of domains with one API call each - curl, Python, CSV export and daily DR tracking.

How to give your AI app live web data

Build a fetch tool for your agent, clean pages for the model and keep RAG sources fresh with rendered, unblocked page fetches.

Connect your AI agent framework to the live web over MCP

Give agents built with the Vercel AI SDK, LangChain or the Claude API a real browser through UnblockingAPI's hosted MCP server.