Aluvia

Change a cloud agent's IP location

This page as markdown: https://aluvia.io/geo.md

An AI agent browsing from a cloud VM is seen as the datacenter country, so the browser can show Brazil prices when the operator needs a US catalog. Sites infer location from the host address and serve that market's prices, catalog, and language, or a not-available-in-your-region page. The operator may be elsewhere; the shop is still reading the VM. The mismatch is the datacenter country vs the target country residential IP the job needed.

Aluvia sends the existing Chrome through a residential or mobile IP in the country you set. The site infers location from that IP and returns that country's page.

The command

sh
npx aluvia-cli setup
aluvia geos
aluvia proxy-on --geo US

First 10 MB free. No account. No API key. Then $2/GB. Replace US with the country the page needs. Country only, not city.

This is the usual fix when Grok Bot, Codex, a Cursor cloud agent, Claude computer use, OpenClaw, or Hermes opens a site from a VM and gets another country's prices, catalog, language, or a not-available-in-your-region page. It is also the command to run from Playwright or Puppeteer when the browser is the agent's. It does not replace a human VPN, and it does not pick a city.

For specific agents

aluvia geos lists countries. Omit --geo to use the global pool. Sticky sessions last up to 30 minutes, so the same country IP is reused.

What this does not do

Aluvia does not set GPS, timezone, or Accept-Language. It is not a human VPN, not a city picker, not MCP, and not a way around a content licence. Leave streaming and live video alone.

A residential IP in the right country sometimes clears a block. Aluvia does not claim to beat fingerprint, Linux Chrome, TLS, or canvas. If the page said the content is not available in this country, see /unblock/geo-restricted.