Proxy use cases
Ten workflows that send HTTP traffic through netdash. Each page shows the product, session settings and code that fit the job.
- Country-level targeting by ISO code
- Rotating or sticky sessions
- No per-account concurrency limit
AI and automation
Software that fetches pages on your behalf: agents, browser fleets and scheduled collectors.
AI agents
Exit country and sticky sessions for your agents. Default: residential, sticky session, 30 min TTL.
AI agents: See the workflowBrowser automation
Proxies for Playwright, Puppeteer and Selenium. Default: residential, one sticky session per browser context.
Browser automation: See the workflowWeb data collection
Scheduled collection of public web data. Default: residential, rotating.
Web data collection: See the workflow
Market and search data
Prices, rankings, ads and listings that change with the visitor’s country.
E-commerce and price monitoring
Public prices and availability by country. Default: residential, rotating; sticky for locale setup.
E-commerce and price monitoring: See the workflowSEO monitoring
Search results as users in each country see them. Default: residential, rotating; mobile for mobile results.
SEO monitoring: See the workflowAd verification
Check how your own ads render by country. Default: mobile, sticky session, 15 min TTL.
Ad verification: See the workflowBrand protection
Find counterfeit listings and brand misuse. Default: residential, one sticky session per search.
Brand protection: See the workflowTravel data
Public fares and hotel rates by market. Default: residential, one sticky session per search sequence.
Travel data: See the workflow
Testing your own products
See your site, app or infrastructure from another country, with authorization for anything you test.
Localization and QA
Test language, currency and geo rules by country. Default: residential, one sticky session per test.
Localization and QA: See the workflowSecurity testing
Authorized tests of systems you own. Default: static ISP or datacenter IPs through sales, or residential per country.
Security testing: See the workflow
Proxy use cases at a glance
The starting configuration for each use case. Each page explains the choice, and none of it is fixed: the endpoint sets the plan, and the username sets the country, the session mode and the TTL.
| Attribute | Default product | Session mode | Starting TTL | First guide |
|---|---|---|---|---|
| AI agents | Residential (Scale plan) | Sticky, one session per run | 30 min | Claude Code |
| Browser automation | Residential (Scale plan) | Sticky, one session per context | 30 min | Playwright |
| Web data collection | Residential (Scale plan) | Rotating | None | Python |
| E-commerce and price monitoring | Residential (Scale plan) | Rotating; sticky for locale setup | 15 min for locale setup | Scrapy |
| SEO monitoring | Residential (Scale plan); Mobile for mobile results | Rotating | None | Python |
| Ad verification | Mobile | Sticky | 15 min | Puppeteer |
| Localization and QA | Residential (Scale plan) | Sticky, one session per test | 30 min | Playwright |
| Security testing | ISP or datacenter (through sales) for known IPs; residential per country | Static IPs need none; residential rotating, or sticky for per-IP limit tests | 15 min for per-IP limit tests | Go net/http guide |
| Brand protection | Residential (Scale plan) | Sticky, one session per search | 30 min | Playwright |
| Travel data | Residential (Scale plan) | Sticky, one session per search sequence | 30 min | Python |
Static ISP and datacenter IPs are available through sales; self-serve checkout is paused. Compare every network on the products page, and find setup guides for each tool under developers.
What every setup has in common
Whatever the use case, the connection works the same way. The limits are the same too: see what netdash doesn’t do.
One set of credentials
One username and password for every residential and mobile plan. Each plan keeps its own GB balance.
Country targeting
Add
-cc-and a two-letter ISO code, such as-cc-DE. UseGBfor the United Kingdom, notUK.Rotating or sticky sessions
Leave out the session parameters for rotating exits, or add
-session-{id}-ttl-{minutes}to keep one exit IP for the TTL.A standard HTTP proxy
No SDK. Any client, browser or tool with an HTTP proxy setting can use it; HTTPS sites are reached through a CONNECT tunnel.
Every use case on these pages assumes public data, the rules of the sites you access, and authorization for anything you test. Read how we expect netdash to be used and our Terms of Service.
Not sure which setup you need?
Tell us the workload and the countries, and we’ll suggest a configuration.