Skip to content
WebScrap

Web Scraping Without a Proxy Gateway to Manage

Requests leave from our own servers. There is no proxy network behind the API, no exit country to pick and nothing to configure: you send the URL and get the page, or named fields as JSON.
See pricing

Run a real request

Render
Extract
Status
...
Elapsed
... ms
Exit country
...
Browser used
...

This console sends a real request and shows you the real response. Five live fetches per session, and the sample targets run as often as you like.

What a request does

One call fetches the page. There is no separate proxy dashboard, no gateway string to paste and no gigabyte meter to watch.

  • Fetched from our own servers: fast, cheap in volume, right for sites that do not fight back.
  • Browser rendering for pages that need JavaScript, with the page waiting for your selector.
  • One fixed location: pages come back as they look from our servers. Country and city targeting are not offered.
  • Concurrency up to 200 requests at once on Scale, 400 on Enterprise.
  • Only successful responses count against your monthly number.

What to expect from sites that filter traffic

Most public pages answer a plain request from a server address, and those come back as a normal response. Some sites block server addresses, ask for a challenge or only serve pages to a logged in browser. A request to such a page comes back as an error and does not touch your counter, so you never pay for it. If you need a specific exit country, a residential address or a session pinned to one address, this API does not offer that. The comparison with proxy based services is in rotating proxies explained and datacenter proxies versus residential.

You pay for the response, not for the attempt

A page that cannot be fetched comes back as an error and never touches your counter: only a successful response does. That is the difference between a proxy bill measured in gigabytes and a plan measured in results.

Limits per plan

See pricing
PlanSuccessful requests per monthConcurrency
Starter50,0005 concurrent requests
Growth250,00050 concurrent requests
Scale1,500,000200 concurrent requests
Enterprise3,000,000400 concurrent requests