Data APIs · billed per successful request
Web Scraper API
An HTTP API in front of the proxy network. You send the target URL and options; it returns the response, handling proxy choice and retries on your behalf.
What it is
Billed per request rather than per byte or per address, which makes cost proportional to the number of pages you need.
You still own parsing. The API returns what the page returned, and does not pretend to know your schema.
Good for
- Teams that want to stop operating proxy rotation and retry logic themselves.
- Predictable per-page cost for collection jobs with a known page count.
Not for
- Workloads where you need byte-level control of every connection. Use the proxies directly.
Specification
| Metered by | Request |
|---|---|
| Interface | HTTPS API with a key from the dashboard |
| Output | The response body as returned by the target |
| Documentation | Parameters and limits are in the API reference |
Prices, limits and country coverage for your account are shown in the dashboard before you pay. See how pricing works.
How to evaluate it
- Work out cost per successful page, not cost per request: price divided by the share of requests that succeed. The cost tool on this site does the arithmetic.
- Check how the API reports a failed attempt and whether you are billed for it.
Works well for
E-commerce price intelligence
Track competitor prices, stock and listings per market, the way a local shopper sees them.
Public web data for AI
Collect public pages for training, evaluation and retrieval, with a provenance trail a data-governance review can follow.
Market and financial research
Gather public filings, listings and announcements at the cadence your research needs.
Test it on your own targets.
Create an account, run the measurement harness against your real workload, and read the numbers before you commit to anything.