Start here: Residential · Rotating

Data Scraping Solution

Run your own crawler through real home-broadband IPs. This page is for teams that already have Scrapy, Playwright, or a custom collector — you need clean egress, not another dashboard.

Buy rotating residential traffic (pay per GB). Use Web Scraping API instead only if you do not want to operate browsers at all — that is a different product, covered on its own page.

Engineers who own the crawler and only need IPs

Crawler teams

You already parse HTML. You need residential exits that survive WAF checks.

Price monitors

High-volume public listings where you control retries and concurrency.

In-house data platforms

ETL already exists — proxy is just the network hop.

Agencies with a scraper stack

One rotating pack, many jobs, GB billed in one place.

What this page is not

If you do not have a crawler, do not start here. If the site is a hard SPA, do not start with datacenter IPs.

🚫

Datacenter 403s

Hosting ASN is the first thing modern sites block. Rotating residential is the default fix.

🔄

Office IP bans

Crawling from corp NAT burns the whole company IP, not just the bot.

🌍

Wrong geo data

Country-level VPN exits return the wrong catalog. Filter extract URLs by city.

⚙️

Retry storms

Unbounded concurrency plus rotate-on-error drains GB and still fails.

🔐

Logged-in crawls

Rotating mid-session kills cookies — that job belongs on static IPs, not this pack.

💸

Buying every SKU

You do not need mobile, business, and datacenter on day one.

Buy this, not the whole catalog

Recommended: Residential rotating. Alternative: Web Scraping API if you would rather POST URLs and get HTML back. Skip static/custom until you have a logged-in session problem.

Product Billing Use it when…
Residential · Rotating Recommended Pay per GB Recommended — public pages, your crawler, pay per GB.
Web Scraping API Credits · pay per success Alternative — no crawler, JS render, pay only on success.

How to start (one recommended path)

Path A — Rotating residential (recommended)

You keep Scrapy/Playwright. We only supply IPs.

  1. Purchase a residential rotating pack (start small).
  2. Set whitelist or user/pass in Authorization.
  3. Generate country/city endpoints via dashboard or /v1/extract.
  4. Rotate per request; cap workers so you do not self-DOS.
Residential proxies →

Path B — Web Scraping API (no crawler)

You send URLs; we return HTML/JSON.

  1. Open the Web Scraping API page instead of this path if you have no collector.
  2. Test one URL in API Center with render if needed.
  3. Bill credits only on success.
  4. Do not also pump the same URLs through rotating GB.
Web Scraping API solution →

Pick one — do not mix these on the same job

Buy rotating residential when

  • You already run a scraper framework.
  • Targets are public pages, not logged-in dashboards.
  • You want TCP-level control of headers and timing.

Buy Web Scraping API when

  • You do not want to maintain headless Chrome.
  • Pages need JS render or anti-bot handled for you.
  • Failed attempts should cost nothing.

First-week checklist

Common questions

Is this the same as Web Scraping API?

No. This page is proxy IP for your crawler. The API fetches pages for you — see solution-scraping-en.html.

Why not datacenter first?

Cheaper until it is not — most retail and search targets block hosting ASN immediately.

When do I need static IPs?

Logged-in sessions, partner allowlists, or seller accounts — see Account or E-commerce solutions.

Mobile proxies?

Only if the target is a mobile app or mobile-only store page — see Mobile App Data.

Can I mix API and proxy on one job?

Yes, but split by URL class: easy volume on rotating, hard pages on API. Do not double-fetch.

Go deeper

Start with one rotating residential pack

If you already have a crawler, this is the SKU. If you do not, open Web Scraping API instead.