Priced per 1,000 successful calls, with the proxies and retries included. Failed calls are free.
Scraper API
Starting at
Web scrapers
116 ready-made endpoints across 23 platforms, each returning parsed JSON from one REST call. Proxies, captchas and parsing are handled server-side, and a call that does not come back does not bill.
$1.49
per 1,000 successful calls
111 endpoints · 23 platforms
$14.90+
up to $38.74 per 1,000 successful calls
5 endpoints · 3 platforms
Each endpoint's price in the catalogFree
for every blocked or errored call
Errors and timeouts never bill · a missing target counts as a call
Social Media
86 endpointsStreaming
9 endpointsMarketplace
6 endpointsBusiness / B2B
6 endpointsLink in Bio
5 endpointsAd Libraries
4 endpointsHow it is priced
The scraper API is priced per thousand requests, and that price includes the proxy, the headless browser where one is needed, and getting past whatever the target is running. You are buying a result, not the ingredients.
Comparing a per-request API to a per-gigabyte proxy directly is the most common pricing mistake in this market. A raw proxy bills you for bandwidth and leaves the browser, the retries and the anti-bot work to you. A scraper API bills for the finished request and absorbs all of that.
The honest way to compare is cost per successfully extracted page, including the bandwidth a headless browser burns and the requests that failed. That number often surprises people in both directions, which is why we publish the components rather than a marketing claim.
Most scraper APIs price in credits, and a request can cost more than one credit depending on what it needed. A JavaScript render, a residential exit or a premium target can each multiply the cost, so a headline per-credit price and the real per-request price can differ by a lot.
We wrote a study on how the industry does this. The reason it is mentioned on our own pricing page is that the same question should be asked of us.
FAQ
Everything about scraper api pricing. Still unsure? Our team replies the same day.
Per thousand requests, at the rate shown on this page. The proxy, the browser and the anti-bot handling are included in that number rather than billed on top.
It depends entirely on your target. Against something undefended, raw proxies are cheaper. Against something that needs a browser and repeated attempts, the API usually wins once you count the bandwidth and the failures.
The unit is a successful request, which is the only way a per-request price is meaningful.
A per-request surcharge for expensive work, like rendering JavaScript or using a residential exit. It is why a headline credit price and a real request price can diverge, and it is worth checking on any provider you compare us with.
Reselling proxies?
The scraper APIs are not on the partner rate card. Every account, resellers included, calls them at the public per-call price.
Or talk to us at support@hproxy.com
