01What are residential proxies and when should you buy them?
Buy residential proxies when a website needs to see your requests as ordinary home visits. A residential proxy routes each request through an IP that an internet provider assigned to a household. To the site on the other end, the connection looks like it came from a regular home router.
ProxyToo rotating residential proxies are a traffic product, not a subscription. There is no order form to fill in, and the GB you use comes straight off your topped up balance. That makes them an easy starting point for teams whose workload changes month to month, for individuals testing proxies for the first time and for analysts who hop between countries.
The same balance also pays for ISP, datacenter, IPv6 and mobile proxies. Start with residential and add other products as your work grows, all from one account.
02How do residential proxies work under the hood?
Your software connects to a single gateway, gate.proxytoo.com:7000, and the gateway picks the exit IP for you. The proxy address in your code stays the same; you only change the username to set the country, city and session.
Conditions are chained into the username with hyphens. For example, user-country-us means a US home IP and user-country-us-city-new_york means a New York home IP. The password field takes your account access token, which starts with pt_. That one token is both your account ID and your proxy password.
Both HTTP and SOCKS5 are supported. HTTP is the simple choice for scraping web pages, while SOCKS5 is handy for browser automation or for passing non web traffic through the proxy.
- One gateway address reaches every country.
- The username sets location and session.
- The password is your pt_ access token.
- HTTP and SOCKS5 both work.
03What are residential proxies best used for?
Residential proxies shine on jobs where the origin of each request matters, the request count is high and results change by location. If two of those three apply, residential proxies are the first product to look at.
Travel fare comparison is a good example. The same flight or hotel can show a different price and page depending on the visitor's country, so you need local home IPs. Tracking listings that refresh every day, such as real estate or job postings by region, also stays stable over time when requests are spread across many IPs.
Brand protection teams hunt for counterfeit listings on shops in many countries. Each region shows different products, so adding city targeting sharpens the results. Localization QA works the same way, checking through real home IPs that visitors in each country see the right language, currency and shipping notes.
- Travel and hotel fare comparison
- Real estate and job listing monitoring
- Brand protection and counterfeit watch
- Localization QA
- Review and reputation monitoring
04How do you target countries and cities with residential proxies?
Set the country with the country value and the city with the city value. You can choose from 60 countries and 175 cities across Asia, Europe, the Americas, the Middle East and Africa, and Oceania.
Country codes are two lowercase letters such as us, jp or gb, and city names with spaces use underscores, as in new_york. Leave the city out and you get IPs from many regions inside that country, which gives you an evenly spread sample when you need country level numbers.
If you are unsure of a spelling, use Create connection details in the dashboard and pick the country and city from a list. The values drop straight into the username, ready to copy. Use a city only for requests that need city level results and keep the rest at country level for a wider pool of IPs.
When you compare many countries in one job, split the work into batches per country and save the country code with each result. If a value looks odd later, you can see right away which country's IP produced it and check again.
05Sticky sessions or rotating IPs: which should you pick?
Pick a sticky session when steps depend on each other and rotation when every request stands alone. Without a session name, each request gets a new IP; with one, you keep the same IP for up to 120 minutes.
Name sessions freely, as in user-country-jp-session-shop1. The same name keeps the same IP and a new name gets a new IP, so numbering them shop1, shop2 and so on gives each worker its own IP.
Sessions fit flows like adding to a cart and checking the page right before checkout, or paging through search results one after another. When requests are independent, like collecting tens of thousands of product pages, rotating per request spreads the load across many IPs and runs more smoothly.
- Use a session name for connected steps.
- Drop the session name for independent requests.
- Give each worker its own session name.
- Split flows so each fits inside one session.
06How much do residential proxies cost?
Residential proxy pricing is $0.78 per GB multiplied by the data you actually move. Upload and download both count, and the charge comes straight from your balance with no order step.
Say a site averages 200 KB per page and you collect 50,000 pages. That is about 10 GB, or about $7.80 at the current rate. Run the same job once a week and a monthly budget of about $31.20 covers four runs.
Bigger top ups earn a bonus, so you get more GB for the same spend. A $100 card adds a 20% bonus for a $120 balance, which is about 153.8 GB of residential traffic. The full bonus ladder is $100 +20%, $200 +25%, $300 +30%, $500 +35%, $1,000 +40%, $3,000 +45%, $5,000 +50%.
Your balance never expires, so you can top up once with a larger card and use it over several months. Whatever is left also works for other products such as ISP or mobile proxies.
07Residential proxies vs other proxy types: which fits your job?
Choose residential when traffic is moderate and location matters, unlimited residential when you move a lot of data every day, ISP when one IP must last a long time and mobile when you need a phone network. If cost comes first and the target accepts datacenter IPs, datacenter proxies are a good pick too.
Unlimited residential is a flat daily rate with no GB counting, and it mixes IPs from many countries. So send requests that need an exact location, like city level search results, through per GB residential proxies and let unlimited handle bulk collection where location does not matter.
ISP proxies give you one IP for months at a time at the same address. ISP is strong where an account's login location must stay fixed and residential is strong where collection needs widely spread requests, so using both gives each a clean role.
08How do you set up residential proxies and fix common issues?
Setup takes four steps. Save your token, top up, create connection details and paste them into your tool. Your pt_ token shows only once at sign up, so copy it, save it to a file and tick "I saved it".
Top ups are made in a secure checkout window with USDT (TRC20, BEP20, ERC20, Solana), USDC (BEP20, ERC20, Solana), BTC, ETH, BNB, SOL or LTC. The checkout shows a deposit address and the exact amount to send, and stays open for 60 minutes. Once the deposit is confirmed, an admin check follows and the balance updates. Each top up ranges from $30 to $5,000.
If a connection fails, check the username spelling and country code first. Then make sure the full token is in the password field and that your balance has funds. Test with the curl format from the dashboard first; once it works, move the same values into Python, Node.js, Scrapy or any other tool to narrow down the cause fast.
- Leave short gaps between requests.
- Match request headers to a real browser.
- Use a different session name per job.
- Test with curl before wiring up your tool.