Prices are rendered by region, so collect them by region
Price monitoring and competitor price scraping
The same product page quotes a different price, tax line and delivery promise in New York than it does in Los Angeles, and a data center IP returns a version no real buyer ever sees. ZapIP routes price monitoring through genuine residential exits in 195 countries with city and ASN targeting, so what you store is what a local shopper is quoted.
- 90M+ residential pool
- City & ASN targeting
- 99.9% request success
- From $0.8/GB
How it works
Collect the price a local buyer actually sees
Marketplaces vary price, tax, stock and delivery windows by where the request comes from. Get the exit wrong and the dataset looks complete but cannot be used to set a price.
- Country exits across 195 regions; city and state in 33 priority markets
- ASN targeting pins the local carrier so you skip the hosting-network variant
- Currency, tax and delivery promises follow the exit — no after-the-fact correction
- Run one SKU across regions in parallel and read the regional spread directly
How it works
Cut the block rate instead of paying for retries
The cost of price scraping is not bandwidth, it is retries. Once an exit is classified as automation, running it again just repeats the same failure more expensively.
- Rotation configurable from 1 to 360 minutes to match each site's throttle
- Sticky sessions up to 90 minutes keep carts and multi-step quote flows alive
- Reputation is checked continuously and flagged addresses retire automatically
- No concurrency cap, so you can push hard inside a narrow promo window
How it works
Pick the billing model your crawl schedule implies
Scheduled sweeps a few times a day belong on traffic; a crawler that never stops belongs on bandwidth. Same network underneath — the difference is how you pay and how hard you can push.
- Traffic from $0.8/GB and it never expires — right for daily or weekly snapshots
- Bandwidth from $32/day for 100Mbps, unmetered — right for round-the-clock coverage
- HTTP(S) and SOCKS5 throughout, with ready snippets for Scrapy and Playwright
- API extraction and sub-accounts to split usage and cost per project
Coverage
One network behind all four products — changing the billing model does not change how you connect or how you target.
All 33 markets- 195 countries & regions
- Available
- All 50 US states
- Available
- City-level targeting
- Precise
- ISP & ASN targeting
- Supported
4 billing models
How this is billed
All four billing models share one network. Short bursts go per GB, pipelines that run continuously go per Mbps, and anything tied to an account identity goes per IP-day or per IP-month.
FAQ
Questions about this solution
Should price monitoring use rotating or static residential proxies?
Almost all competitor price scraping runs on rotating residential proxies. Public price pages need no logged-in identity, and an exit that changes naturally is far less likely to be throttled. Static long-term IPs come in only when you need a signed-in view — a seller back-end wholesale price, or a membership tier tied to the account. Both can run from one account.
Is scraping competitor prices legal?
Collecting publicly displayed prices is standard competitive-intelligence practice, but the boundaries matter: take only what is publicly visible, respect the target's terms and robots directives, collect no personal data, and never work around a login or paywall. ZapIP's acceptable use policy prohibits scraping sensitive personal data and government sites, and violations end the account. For your own jurisdiction, have counsel confirm.
How do I capture local currency and tax-inclusive prices?
Pin the exit to the target city and make your language and timezone headers agree with it. Platforms decide which currency to render mostly from IP geolocation, with account preferences second. ZapIP offers city-level targeting in 33 priority markets and state-level in the US, which matters because US sales tax varies by state and only shows up at checkout, not in the listing.
How much bandwidth does price monitoring need, and what does it cost?
A product page is usually 100–400KB compressed; fetching HTML only and blocking images and static assets, 100,000 pages lands around 15–40GB. At $0.8/GB and down, that is roughly fifteen to thirty dollars a day, falling as volume grows. For a crawler that never stops, the bandwidth plan — 100Mbps from $32/day, unmetered — usually works out cheaper.
Get one request working. Scale after that.
Test before you commit, with an engineer on your integration.