Proxies for AI agents
AI agents that browse the web fetch from datacenter IPs that sites block on sight — so the model gets a CAPTCHA wall instead of the page. Route the agent's HTTP tools through a residential gateway and it reads the real internet, the way a person would. Works with LangChain, browser-use and any tool built on requests or httpx.
Connection details
Swap PROXY_USER / PROXY_PASS for the credentials on your dashboard. New here? Create an account to generate a key.
AI agents (LangChain) proxy example
Steer the exit IP from the username
Tips & gotchas
- Give each agent (or run) its own sticky session id so its IP stays consistent within a task.
- Target the country your task needs — pricing, availability and search results are all geo-specific.
- For headless-browser agents (browser-use, Playwright), use the Playwright setup on this site.
AI agents (LangChain), answered
Why do AI agents need residential proxies?
Agents run in cloud environments whose datacenter IPs are widely blocklisted, so web tools hit CAPTCHAs and 403s. A residential IP looks like an ordinary home visitor, so the agent actually retrieves pages instead of block screens.
Does this work with browser-use or a headless-browser agent?
Yes. For agents that drive a real browser, launch it through the proxy using our Playwright or Puppeteer setup. For agents that fetch URLs directly, the requests/httpx setup above is enough.
How do I keep an agent on one IP for a whole task?
Add a sticky session id to the username (PROXY_USER__sessid.task42;sessttl.30). The agent then keeps the same residential IP for up to 30 minutes, so multi-step tasks behind a login stay coherent.
Ready to route AI agents (LangChain) through residential IPs?
Create an account, paste the code above, and we'll add your first 1 GB of residential free on your first top-up. Pay by the GB after that — no subscription.