Web Scraping API with Built-In Proxy Rotation
Scrape geo-restricted and heavily protected sites through a managed proxy pool, no separate proxy vendor to run yourself.
Proxies are a separate job
Buying proxies means a separate bill
You still have to write your own rotation and retry logic
And after all that, you still need to build the scraper itself
One parameter
Multi-provider backendproxyMode: "auto"tries the request directly first and only retries through a proxy if the site blocks itproxyCountryroutes the request to appear from a specific countryRuns across multiple proxy providers on our backend for better reliability
Simply use the proxyMode and proxyCountry parameters on our Web Scraping API.
Proxy handling built into every request
Country-level geo-targeting
Set proxyCountry to fetch a page as it appears in a specific country, useful for region-locked pricing, content, or availability.
Smart retry with proxyMode
Requests try directly first. A proxy only kicks in, and only gets billed, when the site actually blocks the attempt.
Stealth mode and waitTime
Pair proxy routing with stealth and waitTime for the most restrictive sites.
Frequently Asked Questions
No. Proxy routing is fully managed on our end through proxyMode and proxyCountry.
true always routes the request through a proxy. "auto" tries the request directly first and only falls back to a proxy if the site blocks it, so you're not paying the proxy premium on requests that didn't need one.
A standard request is 1 credit. When a proxy is used (proxyMode: true, or "auto" after a block), that's 4 additional credits, 5 total for that request. Proxy routing isn't included on the Free plan, you'll need a paid subscription or a credit pack to use proxyMode.
No. This is a reliability and geo-targeting feature of the Web Scraping API for fetching and rendering pages, not a general-purpose proxy you can route arbitrary traffic through. If you need raw proxy access for something else, you'll still need a standalone proxy provider.
Yes. proxyMode, stealth, and waitTime are independent parameters that stack on the same request, useful together for sites with both geo-restrictions and heavy bot detection.