A residential proxy for AI agents is the household exit one agent task keeps for its whole run. The agent opens a browser or an HTTP client, checks the country, reads a public page, and closes. The next task gets a new session id. Rotating under an open task moves the IP while cookies, and any timezone taken at launch, stay on the first address. Premium HTTP on port 2099 is the country pool. Elite HTTP on port 5499 adds a supported city or ISP when the page scores the exit, and it does not guarantee acceptance. Sticky holds a rotating-pool IP for 1–1440 minutes, default 30. That is long enough for one task, and it is not a dedicated address. The local-browser how-to is the Browser MCP docs and the two existing MCP articles. This page is the buying decision: which pool, and one session per task. Public pages only. No login automation and no challenge solver.
Key Benefits
The Challenges We Solve
How It Works
Start the task with a new session id and a lifetime that covers the run.
Read an IP-lookup URL and confirm the country before the target page.
Keep every step of that task on the same username.
Close the task. The next task uses a new session id.
Premium or Elite for this job?
This use case usually needs Elite — higher-reputation exits plus city and ISP targeting. Premium still works for volume on easier hosts.
Premium for volume. Elite when anti-bot is the job.
| Premium | Elite | |
|---|---|---|
| Targeting | Country | Country, city, ISP |
| Session | Rotating or sticky | Rotating or sticky |
| Best for | Scale crawls, SEO, pricing | Cloudflare, Akamai, DataDome |
