Residential and mobile proxies over standard HTTP. One credential pair, country targeting, rotating or sticky sessions.
Proxy URL, Brazil exit
http://USERNAME-cc-BR:PASSWORD@scale-us.netdash.io:2000Any client that speaks HTTP.Guides for the ones you use.
Integration guides cover cURL, Python, Node.js, Go, Scrapy, Playwright, Puppeteer, Selenium, Chrome, Docker, Cursor, Claude Code, OpenAI Agents SDK, LangChain, MCP.
Traffic enters through the gateway for its region and leaves through an IP in the country you set. Choose both below, or click a country on the map.
Residential and mobile traffic enters through the -us gateway for exits in the Americas or the -eu gateway for exits in Europe, Africa and Asia, and leaves through an IP in the country you set with -cc- and a two-letter ISO code.
Static ISP IPs are in Ashburn, Frankfurt, London and Sydney; datacenter IPs are in the United States, Germany, the United Kingdom and the Netherlands. To confirm availability for a specific country, email support, or see proxy locations and gateways.
Your route
Through the gateway to an exit IP in , , on the plan.
Proxy URL
http://USERNAME-cc-US:PASSWORD@scale-us.netdash.io:2000Replace USERNAME and PASSWORD with the credentials from your dashboard.
Scale, Americas gateway, exit IP in United States, rotating.
The host picks the plan and gateway; the options travel in the username. Every host, port and export format is in the proxy format reference.
http://USERNAME-cc-US-session-a1b2c3d4-ttl-30:PASSWORD@scale-us.netdash.io:2000
USERNAMEOne username and password work on every residential and mobile plan. Each plan keeps its own GB balance.
-cc-USSet the exit country with a two-letter ISO code, such as -cc-DE. Use GB for the United Kingdom.
-session-a1b2c3d4-ttl-30Leave out the session parameters and the gateway assigns exit IPs for you, or reuse a session ID to keep one exit IP for the TTL you set while that IP stays available. Dashboard presets run from 15 minutes to 7 days.
Your route: rotating, so it is left out.
scale-us.netdash.io:2000All residential plans and Mobile use the same username syntax, so moving a workload to another plan means changing the host and port.
What every residential and mobile plan comes with.
If your client, browser or tool supports an HTTP proxy with a username and password, it works with netdash. HTTPS websites go through a CONNECT tunnel.
netdash sets no per-account limit on concurrent connections or threads. You set the rate per website, within what each site can handle.
Residential and mobile GB are one-time purchases with graduated pricing, and purchased GB never expire.
Every price band is public, the calculator works out an order's total band by band, and 1 GB of traffic is 1 GB from your balance.
Create an account with email, a password and a one-time code, or with Google or Discord. Then buy a residential or mobile plan from 1 GB; it's provisioned automatically once payment is confirmed.
See pricingIn the dashboard, open Residential (or Mobile) and choose Generate. One username and password cover every residential and mobile plan.
Set the host and port for your plan and gateway, then add the exit country and an optional sticky session to the username.
Proxy formatSend one cURL request through the proxy to https://api.ipify.org?format=json and check the exit IP it returns.
Pick the guide for your language, browser tool or agent framework, and set the proxy on the client that fetches pages.
All integration guidescurl --max-time 30 -x "http://USERNAME-cc-US:PASSWORD@scale-us.netdash.io:2000" \
"https://api.ipify.org?format=json"import requests
proxy = "http://USERNAME-cc-US:PASSWORD@scale-us.netdash.io:2000"
proxies = {"http": proxy, "https": proxy} # set both, or HTTPS requests bypass the proxy
response = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=30)
response.raise_for_status()
print(response.text)import { ProxyAgent, fetch } from "undici";
const dispatcher = new ProxyAgent({
uri: "http://scale-us.netdash.io:2000",
token: "Basic " + Buffer.from("USERNAME-cc-US:PASSWORD").toString("base64"),
});
const res = await fetch("https://api.ipify.org?format=json", { dispatcher, signal: AbortSignal.timeout(30_000) });
console.log(await res.text());import { chromium } from "playwright";
const browser = await chromium.launch({
proxy: {
server: "http://scale-us.netdash.io:2000",
username: "USERNAME-cc-US",
password: "PASSWORD",
},
});
const page = await browser.newPage();
await page.goto("https://api.ipify.org?format=json");
console.log(await page.textContent("body"));
await browser.close();Example output
{"ip":"203.0.113.10"}Your output shows a different address in the country you chose.
An AI agent decides what to look up, and its browser or HTTP client does the fetching. Configure netdash as that client's proxy, pick the exit country with -cc- for each task, and use a sticky session to keep a multi-step task on one exit IP for the TTL you set.
Keep the credentials in environment variables; one pair works for every residential and mobile plan. Set the proxy on the client rather than with a global HTTPS_PROXY: tools such as Claude Code also route their own model API traffic through the proxy that variable names.
netdash doesn't solve challenges. If a site shows a CAPTCHA or a login wall, design the agent to stop and hand off to a person. Read more about proxies for AI agents.
Setup guides for the coding assistants, frameworks and browsers that agents run on.
Let your coding assistant add netdash to a project: credentials in .env, proxy settings per client, and a Playwright MCP server that sends its browser through a gateway.
Browser Use, the OpenAI Agents SDK and LangChain: where the proxy goes on the browsers and HTTP tools an agent calls.
Browsers on cloud VMs, in containers or with a hosted service: which layer does what, and where the netdash proxy fits.
Proxy and authentication settings for Playwright, Puppeteer and Selenium, for end-to-end tests and permitted workflows.
llms.txt starts with the connection facts and links the Markdown version of every doc and guide, so a coding agent can read hosts, ports and the username syntax directly.
The full workflow: an exit country per task, a sticky session per run, and the point where an agent should stop and hand off.
Residential and mobile proxies are billed per GB and share your account credentials. Static ISP and datacenter IPs are billed per IP every 30 days and are available through sales while self-serve checkout is paused. Compare proxy types or see all products.
Residential IPs for location-aware requests and public data collection.
Move between plans by changing the host and port. The username stays the same.
Residential proxiesMobile exit IPs for testing how apps and sites behave for mobile users.
Same username on residential and mobile; the host and port pick the network.
Mobile proxiesAshburn, Frankfurt, London, Sydney
Self-serve checkout is paused. Contact sales for availability.
United States, Germany, United Kingdom, Netherlands
Self-serve checkout is paused. Contact sales for availability.
See all four side by side: the exit IP, locations, billing and how to start.
Compare proxy typesResidential and mobile pricing is graduated per order from 1 to 50,000 GB, and purchased GB never expire. Static ISP IPs are $1.60 per IP per 30 days ($1.40 in /24 subnets) and datacenter IPs $1.40; both cost $1.30 per IP from four subnets, through sales. See pricing and the calculator.
250 GB of Scale
$520.00
Each GB is charged at the rate of the band it falls into, so larger orders lower the average.
All Scale bands250 GB of Scale: $520.00.
ISP, static per IP$1.60 per IP per 30 days, $1.40 in /24 subnets, $1.30 from 4 subnets
Datacenter, static per IP$1.40 per IP per 30 days, $1.30 from 4 subnets
Through sales.Contact sales
Purchased GB never expire. Prices in USD, from the live price list.
Open the price calculatorWe publish what we can verify and say plainly what isn't included.
netdash forwards your traffic unchanged, so a challenge reaches your client exactly as the website sent it.
You choose the exit country; you can't select a city, region, ZIP code, ASN or carrier.
Every request uses your username and password.
None is needed: it's a standard HTTP proxy, and usage lives in the dashboard.
We don't publish uptime figures or offer an SLA.
netdash is for lawful, authorized work. Section 2 of our Terms of Service sets the binding rules. Read how we expect netdash to be used.
Respect robots.txt and each site's terms, keep request rates reasonable, and don't collect personal data without a lawful basis.
netdash forwards traffic unchanged and solves no challenges. If a site rate-limits or challenges you, slow down, check its terms or use its official API.
Run security and geo tests only against systems you own or have written permission to test.
Seen netdash used in a way these rules forbid? Read how to report misuse.
Residential and mobile share credentials and syntax, so you can move a workload between them by changing the host and port. ISP and datacenter IPs are static and come as their own host:port:user:pass list.
Exit IP
Rotating, or sticky for the TTL you set
Exit IP
Rotating, or sticky for the TTL you set
Exit IP
Static while the subscription renews
Exit IP
Static while the subscription renews
Need every attribute side by side? Compare proxy types.
Each workflow has its own page with configuration, code and responsible-use notes.
All use casesScheduled collection of public pages by country, at a rate the site can handle.
Public product prices, currency and availability in each market you track.
Search results as they appear in each country, for rank checks you can repeat.
Check how your own ads render by country, from the placement to the landing page.
Language, currency, consent banners and geo-redirects as visitors in each country see them.
Authorized tests of systems you own: geo rules, rate limits and WAF policies from other countries.
Find counterfeit listings and unauthorized sellers on public pages in other markets.
Public flight fares and hotel rates by point of sale.
Each guide shows the proxy setup for one tool, with copyable code that reads your credentials from environment variables. Every guide and doc also has a Markdown version, and llms.txt indexes them for coding agents. Browse all integration guides or the netdash documentation.
Credentials, your first request and how to check the exit IP.
Hosts and ports for every plan, the username syntax and the export formats.
requests, httpx and aiohttp, with sticky sessions and error handling.
undici ProxyAgent and axios, with authentication and timeouts.
A net/http Transport with an authenticated proxy, sticky sessions and timeouts.
Per-request proxies or a downloader middleware, with polite crawl settings.
Proxies per browser or per context, for Node.js and Python.
An authenticated proxy per browser, with the exit country set in the username.
Proxy authentication for WebDriver sessions, with the exit country set in the username.
The editor’s own proxy settings and HTTP/2, plus a netdash proxy for the code its agent runs.
Rotating or sticky exit IPs, session IDs and the TTL presets.
407 errors, timeouts, requests that skip the proxy and the wrong exit country.
More answers on the proxy FAQ.
netdash is proxy infrastructure for developers, AI agents and data teams. Residential and mobile proxies, sold per GB, share one credential pair, one username syntax, country targeting and rotating or sticky sessions over standard HTTP, and purchased GB never expire. Static ISP and datacenter IPs are available through sales.
Point any HTTP client, browser or tool that supports an authenticated HTTP proxy at your plan's gateway, for example scale-us.netdash.io:2000. Authenticate with your username plus options (USERNAME-cc-US) and your password. HTTPS websites work through a CONNECT tunnel. The quickstart walks through it.
Your proxy username and password from the dashboard (not your sign-in password) work on every residential and mobile plan, and each plan keeps its own GB balance. Static ISP and datacenter IPs are delivered as their own list in host:port:user:pass format, with the credentials for that order.
Residential and mobile GB are one-time purchases in USD with graduated pricing: each GB in an order is charged at the rate of the band it falls into, from 1 to 50,000 GB per order. Purchased GB never expire, and you pay by card through Stripe. The smallest order is 1 GB. The pricing page lists every band and has a calculator.
No. netdash sets no per-account concurrency or thread limit, and you pay for the traffic you use: 1 GB of traffic is 1 GB from your balance. Set your own limit per website so your requests stay within what each site can handle.
No. netdash forwards your traffic unchanged and does not solve CAPTCHAs, render JavaScript or retry requests, so a challenge reaches your client exactly as the website sent it. Treat it as a signal to slow down, check the site's terms or stop.
Self-serve checkout for both is paused. Contact sales for availability: ISP inquiry or datacenter inquiry. ISP IPs are $1.60 and datacenter IPs $1.40 per IP every 30 days; ISP /24 subnets are $1.40 per IP, and both cost $1.30 per IP from four subnets.
Create an account, buy from 1 GB and connect with one username and password. Custom terms or static IPs? See enterprise or contact sales.
Privacy choices
We use cookies and similar technologies that this site needs to work and to remember your choice. We also use Google Analytics to understand which pages and features people use: in the EEA, the UK and Switzerland only with your consent. Live chat loads only if you open it. You can change your choice at any time under “Privacy choices” in the footer. Privacy Policy