Rotating Residential Proxies that spread your requests across home IPs

Your tool always connects to one place: gate.proxymay.com:7000. When the gateway receives a request, it reads the conditions in your username, picks a home IP that matches them, and forwards the request to the target site from that IP. The target sees the home IP, not your server.

If the username has no session, every request gets a new IP. Send 1,000 requests and they leave from many different homes, which keeps any single address from hitting rate limits. There is no proxy list to maintain and no IPs to cycle by hand.

Add session-name and you keep the same IP for as long as you reuse that name, up to 120 minutes. This is a sticky session. It suits short multi-step flows, like adding an item to a cart and moving on to the next page.

If you need one IP for hours or weeks, a static ISP proxy that keeps the same IP all month is the better fit.

All four ProxyMay products share one balance, but each has a clear job. Rotating residential is strongest at splitting many requests across many addresses; the other three each win somewhere else.

If you manage accounts on the same IP for weeks, static ISP proxies are the better choice. If you skim public pages that barely block anyone, datacenter proxies finish the job for less. If you need to see what phone users see, pick mobile proxies.

But when the target often blocks datacenter addresses, the request count runs into the tens of thousands, and you need results from several cities side by side, rotating residential is the safest default. That is also why we suggest it to anyone using proxies for the first time.

The address stays the same for every job; only the username changes. The password is always your account access token.

• Price monitoring: checking product pages across several stores a few times a day. A new IP per request means no single address keeps showing up. A country alone, like user-country-us, is usually enough.
• SEO rank checks: search results differ by city. Targeting user-country-gb-city-manchester gets you close to what local users see.
• Ad verification: confirming an ad really shows in a given city requires a home IP in that city.
• Public data collection: high-volume jobs, such as public text for AI training or product listings, run more smoothly the wider you spread the requests.
• Multi-step flow checks: for linked pages like search, detail and cart, add a session- name to keep one IP.

# New US IP on every request
curl -x http://user-country-us:[email protected]:7000 https://ipinfo.io/json

# Keep a Tokyo IP under the session name shop1
curl -x http://user-country-jp-city-tokyo-session-shop1:[email protected]:7000 https://ipinfo.io/json

# Frankfurt, Germany over SOCKS5
curl -x socks5://user-country-de-city-frankfurt:[email protected]:7000 https://ipinfo.io/json

Running several workers at once? Give each one its own session name. Different names like session-w1 and session-w2 get different IPs, while workers sharing a name share an IP. Session names use letters and digits, up to 16 characters.

Rotating residential proxies are billed by data transferred, not by IP count. Pricing starts at $0.80/GB, and the balance goes down by the traffic of each request and response. The number of IPs you pass through does not affect the price, so spreading requests wider costs nothing extra.

For example, $100 at $0.80/GB is 125 GB. If a product page averages 400 KB, 1 GB covers about 2,500 pages, and 125 GB covers about 312,500. Page sizes vary by site, so run a few hundred requests first and measure the real average.

Blocking images, video and fonts cuts data sharply for the same number of pages. With a headless browser, turn on resource blocking first. If you only need the HTML, a plain HTTP request is far lighter than a browser.

1. 1Sign up and get your access token. It is shown only once, so store it somewhere safe right away.
2. 2Top up your balance. The same balance works for all four products.
3. 3Copy a connection format from the dashboard (http, socks5, host:port:user:token) or build the username yourself.
4. 4Enter host gate.proxymay.com, port 7000, the username and your token in your tool's proxy settings.
5. 5Run the dashboard's curl check against ipinfo.io and confirm the country and city.

Any tool that takes a proxy address, like Python, Node.js, Scrapy or Puppeteer, works with nothing extra to install. Tool-by-tool settings are in Quick start.

Rotating residential proxies cover 60 countries and 175 cities. The rule is simple: if results only change by country, set the country; if they change by city, as with local search or local ads, set the city too.

The narrower the city, the smaller the pool of IPs you draw from. Unless you truly need a city, staying at country level gives a better spread.

Write city names in lowercase with spaces as underscores: New York is city-new_york, Los Angeles is city-los_angeles. City lists per country are on Coverage, and a popular example like the United States IP page shows the format at a glance.

Home IPs still get blocked. Send too many requests to one site in a short time and the request pattern itself stands out, whatever the IP.

• When 403 and 429 responses rise, widen the gap between requests and run fewer workers.
• If a sticky session gets blocked, change the session name and start again on a new IP.
• Do not retry failures right away; back off a little longer each time.
• Check robots.txt and the terms of service, and skip areas the site does not allow.

Public data collection, ad verification, SEO rank checks, price monitoring, site testing and managing your own accounts are allowed. Unauthorized access to other people's accounts, spam, fraud, attacks, illegal content, or anything else that breaks the law or a site's rights is forbidden.

Top up a small amount, run one collection job, measure the data per page, then scale as far as you need. Whatever balance remains works on the other three products too. See top-up sizes and bonuses on Plans, then sign up to get your token.