Residential proxies. Bandwidth, not requests.
Real residential IPs across 100+ countries via standard HTTP/HTTPS proxy. Country, state, and city targeting in the username; sticky sessions when you need them; unlimited concurrency. Billed by GB, from $3/GB at scale.
Pay only for bandwidth · unlimited concurrency · cancel anytime
# Connect via residential proxy, US exit, sticky 10-min session
$ curl --proxytunnel \
--proxy "https://residential.scrapingant.com" \
--proxy-user "customer-USER-country-us-sessionid-abc123:PASS" \
"https://target-site.com"import requests
proxy = (
'http://customer-USER-country-us-sessionid-abc123:'
'PASS@residential.scrapingant.com:8080'
)
r = requests.get(
'https://target-site.com',
proxies={'http': proxy, 'https': proxy},
verify=False,
)
print(r.text)import { HttpsProxyAgent } from 'https-proxy-agent';
const agent = new HttpsProxyAgent(
'http://customer-USER-country-us-sessionid-abc123:' +
'PASS@residential.scrapingant.com:8080',
);
const res = await fetch(
'https://target-site.com',
{ agent, dispatcher: agent },
);
console.log(await res.text());Why residential.
Real ISP IPs. No request metering. Drop into any HTTP client without an SDK.
Standard HTTP proxy. Parameters in the username.
No SDK, no API client to install. Point any HTTP library at residential.scrapingant.com:8080 (or :443 for HTTPS) and pack country, state, city, and session into the username — separated by hyphens. Password is your residential key. If you also want managed Headless Chrome rendering and retries on top, switch to the Web Scraping API with proxy_type=residential.
- Works with curl, requests, axios, fetch — anything that speaks HTTP proxy
- HTTP on
:8080, HTTPS on:443 - Username syntax:
customer-USER-country-us-sessionid-id
100+ countries. City > state > country.
Target by ISO country code (country-us), US state (state-us_california), or city (city-us_los_angeles). City wins over state, state wins over country — so the most specific parameter you set is the one we route through.
- 100+ countries via ISO codes
- State-level targeting in the US (
state-us_california) - City-level targeting (
city-us_los_angeles)
Stick to one IP when the flow needs it.
Some flows break if the IP rotates mid-flight — login → search → checkout, multi-step OAuth, anything that bakes IP into a cookie. Append -sessionid-anything to the proxy username and we keep the same residential exit for that string. Sessions persist for up to 10 minutes idle.
- Sticky session via
sessionid-anything - ~10 min idle expiry — change string to rotate
- Drop the param for per-request rotation
Unlimited concurrency. No per-IP rate limits.
There's no concurrency cap on the residential plan — open as many parallel connections as your code can handle, we distribute exits across the pool. No per-IP rate limit you have to manage from your client. Push 100 workers, push 10,000. Need a cheaper, faster alternative for low-friction targets? Datacenter proxies bill at $0.44–$0.60 / GB on the same flat-username scheme.
- No concurrency tax on any tier
- Pool selects fresh IPs across requests automatically
- Failed connections never count against bandwidth
What teams use residential proxies for.
Targets where datacenter IPs get blocked and geographic accuracy matters.
Real estate & classifieds
Pull listings, prices, and history from regional portals where IP origin matters.
Talk to sales →SERP & search results
Scrape Google, Bing, Yandex, and regional engines with country-accurate rankings.
Talk to sales →Brand & content monitoring
Watch reviews, news, and forums from each region — see the page real users see.
Talk to sales →Ad verification
Verify ad placements appear in target geographies, not just from your office IP.
Talk to sales →Sneaker & ticket flows
Stick to one IP across login → cart → checkout with sticky sessions, no flagging.
Talk to sales →AI agents on the open web
Give your agent geo-aware access to region-restricted content and local search.
Talk to sales →Bandwidth tiers, no request metering.
Pay only for the bandwidth you use. Unlimited concurrency, no setup fees, no per-request math. Cancel anytime.
- 100+ countries
- Unlimited concurrency
- 5 GB bandwidth
- Email support
- 100+ countries
- Unlimited concurrency
- 10 GB bandwidth
- Email support
- 100+ countries
- Unlimited concurrency
- 25 GB bandwidth
- Email support
- Priority support queue
…and custom plans for higher volume.
- 100+ countries
- Unlimited concurrency
- 50 GB bandwidth
- Priority support
- 100+ countries
- Unlimited concurrency
- 100 GB bandwidth
- Account manager
- 100+ countries
- Unlimited concurrency
- 250 GB bandwidth
- Account manager
- 100+ countries
- Unlimited concurrency
- 500 GB bandwidth
- Account manager
What teams are saying.
From solo developers shipping side projects to enterprise pipelines at Fortune 500s.
★★★★★ 5.0 on Capterra →★★★★★“Onboarding and API integration was smooth and clear. Everything works great. The support was excellent.”
★★★★★“Great communication with co-founders helped me to get the job done. Great proxy diversity and good price.”
★★★★★“This product helps me to scale and extend my business. The setup is easy and support is really good.”
Frequently asked questions.
Still curious? Get in touch with our team — we usually reply within hours.
What is a residential proxy?
A residential proxy is an HTTP/HTTPS proxy that routes requests through real consumer-ISP IP addresses — the same kind a regular laptop uses on home Wi-Fi from Comcast, Telekom, BT, etc. Anti-bot systems treat residential IPs as ordinary human traffic, which makes them the standard choice for scraping tough targets like ecommerce, sneakers, social platforms, and Cloudflare-protected sites. ScrapingAnt's residential proxy pool covers 3M+ IPs across 100+ countries, billed by bandwidth.
How are residential proxies different from datacenter proxies?
Residential IPs come from real consumer ISPs (Comcast, Telekom, BT, etc.) — the same kind your laptop uses on home Wi-Fi. Anti-bot systems treat them as ordinary human traffic, so they're the right choice for tough targets like Amazon, sneakers, social, and Cloudflare-protected sites.
Datacenter proxies ride backbone fiber from cloud regions — cheaper ($0.44–$0.60 / GB) and faster, but easier to flag. Pick by target, not by preference.
How do I connect to the rotating residential proxy?
Point your HTTP client at residential.scrapingant.com:8080 (HTTP) or :443 (HTTPS). Username encodes parameters: customer-USERNAME-country-us; password is your residential proxy key from app.scrapingant.com/residential. No SDK needed — works with curl, requests, axios, or any HTTP / proxy library. By default every request gets a fresh residential IP from the pool.
How do I target a specific country, state, or city?
Add the parameter to the proxy username: customer-USER-country-us, customer-USER-state-us_california, or customer-USER-city-us_los_angeles. City takes priority over state, state over country. We support 100+ countries with state and city granularity in major regions — useful for localized pricing, geo-restricted catalogs, and locale-specific search results.
How do sticky sessions work on residential proxies?
Append -sessionid-anything to the username — e.g. customer-USER-country-us-sessionid-flow123. We'll pin the same residential IP for that session for up to 10 minutes idle. Change the value to rotate, drop it for per-request rotation. Sticky sessions are useful when a target site bakes the IP into a cookie — login, checkout, or multi-step OAuth flows.
Are concurrent connections limited on the residential pool?
No. Run as many parallel connections as your code can manage — there's no per-account concurrency cap on residential proxies and no per-IP rate limit you're responsible for. Push your worker pool; we distribute exits across the 3M+ IP fleet.
How are residential proxies billed — per request or per GB?
Per GB of bandwidth used. Plans run from 5 GB at $30 ($6/GB) up to 500 GB at $1750 ($3.50/GB). No per-request fees, no concurrency tax, no setup costs. Bandwidth pricing is separate from the credit-based Web Scraping API — proxies bill by GB, the API bills per request. Need higher volume? Get in touch for custom pricing.
When should I use the residential proxy directly versus the Web Scraping API?
Use the residential proxy when you already have your own scraper / browser stack and just need clean residential exits. Use the Web Scraping API when you also want managed Headless Chrome rendering, retries, and a single endpoint that flips proxy_type=residential on the same call. The proxy is the primitive; the API is the managed layer on top — same residential pool underneath.
Need a custom residential plan?
Higher monthly bandwidth, dedicated regions, custom rotation rules, or specific city-level targeting — drop us a line and a real human gets back within a few hours.
“Our clients are pleasantly surprised by the response speed of our team.”
