Proxies for marketplace parsing
Price and assortment monitoring means regular, uniform requests to the same product cards. That traffic profile is the one platforms notice fastest: from a single address it looks like automated collection, which is what it is. A pool of addresses spreads the requests and lets you pull data on a schedule.
From 1 375 ₽ a month for 100 threads.
Threads in the plan
The address is held for a set time
Traffic on rotating plans
Both protocols
The load profile of price monitoring
The job usually reduces to walking a fixed list of SKUs at a known interval. The volume is predictable: number of items times collection frequency. The required thread count follows from that — it depends not on catalogue size but on the window you need to cover it in.
When timed rotation is required
Some platforms serve a product card only inside an established session: a cookie is issued first, then the content opens against it. Per-request rotation breaks that chain. For those cases use timed rotation — the address lives long enough for the steps to complete from one IP.
Scheduling and automation
Scheduled collection is easier to run with IP authentication: the machine goes into the whitelist and the script never stores a password. If the pool is only needed while collection runs, the plan can be bought and renewed through the REST API — the infrastructure then exists for exactly as long as the job does.
What people take for this
Three products. The difference is the address type and whether it changes: some jobs need a pool, others a single fixed IP.
- 10 different /29 networks
- Rotation: per-request or time-based
- Connections as you need
- HTTP, SOCKS5
- User/pass and IP — at once
- 10,000+ rotating IPs
- Rotation: per-request
- Connections as you need
- HTTP, SOCKS5
- User/pass and IP — at once
- 15,000+ static IPv4
- Dedicated stable IPs
- HTTP, HTTPS, SOCKS5
- User/pass and IP — at once
How to connect
Setup fits in one line: the program only needs a gateway host and port. Rotation happens on our side — the program never has to know about it.
- 1Pick a plan
The plan's thread count must be at least what the program is set to, or some connections will sit waiting for a free slot.
- 2Get the credentials
Gateway host, HTTP and SOCKS5 ports, login and password appear in the dashboard right after payment.
- 3Paste it into the program
One address instead of a list: any field that takes a normal proxy server with authentication will do.
Frequently asked questions
Short answers to what gets asked before ordering. Everything else goes to support, which answers around the clock.
How many threads does catalogue monitoring need?
Work back from the collection window. Ten thousand items in an hour is roughly three requests per second; allowing for response time and retries, 50–100 threads is enough. Covering the same list in five minutes needs an order of magnitude more. Calculate from the deadline, not from catalogue size.Do local platforms require local addresses?
Not necessarily, but results can differ: some content and pricing depends on the region a request comes from. If you need the data exactly as a shopper in a given country sees it, use addresses from that country. The rotating IPv6 pool includes Russia; IPv4 offers eleven countries.Does IPv6 work for marketplaces?
Test it on the specific platform. Some sites do not accept IPv6 connections, in which case only IPv4 will work regardless of proxy settings. IPv6 costs less at the same thread count, so it is worth trying against your target first and moving to IPv4 only if IPv6 gets no response.Is this data collection legal?
Proxies are transport, and responsibility for the nature of requests rests with the client. Collecting publicly available data that a platform publishes to all visitors is ordinary competitive analysis. You should check the specific site's terms of use and the regulation that applies to you yourself.
Other use cases
- For multi-threaded software
- For parsing and scraping
- For antidetect browsers
- For captcha software
- For SEO and SERP checks
- Rotating IPv6 and IPv4
- IPv6 proxies
- Static datacenter IPv4
Covered in the blog
- Deep diveProxies for marketplace price monitoring: how many addresses a catalogue needsHonest maths instead of undetectability promises: turning product count and refresh frequency into thread count and a sustainable request rate.Read
- Troubleshooting403 through a proxy: the site refused, the proxy refused, or the address is not the problemA 403 can come from the proxy or from the target site, and they cannot always be told apart. Where to find the Cloudflare code, which codes no address change will fix, and why proxy headers are a poor test.Read
A pool for price monitoring
Rotating plans with timed rotation for sessions. IPv6 from 650 ₽ for 50 threads, with a selectable country. IPv4 from 1375 ₽ for 100 threads, countries assigned at random.