Agents in the cloud use datacenter IPs that often get blocked or hit CAPTCHAs. Aluvia routes web traffic through residential or mobile IPs, unblocking browser workflows.
Copy-paste to any agent.
Works with Grok Bot, Codex, Claude, OpenClaw, and Hermes.
Websites are more suspicious of traffic coming from datacenter and cloud IPs. Humans don't live in datacenters.
When agents use their browser with a datacenter IP, they hit 403 blocks, CAPTCHAs, and throttling. Workflows stall, stay incomplete, or fail.
Aluvia runs a small proxy next to the agent. One command turns it on, and every tab goes out through a residential or mobile carrier IP.
Nothing else changes. Same browser, same tabs, same cookies — and no restart.
Germany · EUR
Show pricesAgents are stuck with the geo of whatever datacenter they are running in. Many workflows require agents to have a different geo IP.
With Aluvia, agents can select an IP from a specific country.
Premium IPs from top providers. Tested for speed and reliability. Best possible pricing.
$ aluvia proxy-on { "egress": "aluvia", "targetGeo": null, "next": "Reload the tab." }
Use your own proxies. Aluvia accepts a standard HTTP or HTTPS proxy URL.
$ aluvia proxy-provider <url> { "provider": "custom" }
Agents just run aluvia setup to get started with a free trial.
Grab an API key from the Aluvia Dashboard to keep using.
$ aluvia auth <key> { "status": "authenticated" }
Every command prints JSON on stdout with a next field. An agent reads next and knows what to run. If aluvia is not on the PATH, put npx aluvia-cli in front of it.
aluvia setup | Sets up Aluvia on the agent's machine. |
|---|---|
aluvia proxy-on | Send every tab through Aluvia, then reload the page. |
aluvia proxy-on --geo US | Use an IP in a specific country. Run aluvia geos for the list. |
aluvia proxy-off | Go back to the machine's own IP. The browser keeps running. |
aluvia rotate-ip | Get a new exit IP when the current one is still blocked. |
