Shellroute Documentation

Shellroute is a CLI tool that lets developers and agents route terminal sessions through country and city-specific proxy exits without changing system-wide network settings.

How it works: install the CLI, run shellroute login, then /connect US. Everything in that shell routes through the selected exit. Everything else stays untouched.

Why shellroute

Developers need proxy access that works like a terminal tool, not a dashboard. Shellroute gives you session-scoped routing, pay-per-GB billing, and a kill switch that ensures traffic fails rather than leaks.

Session-scoped

Only the shell you start is proxied. Your browser, other terminals, and system processes are never affected.

Kill switch

Traffic fails (connection refused) if the proxy tunnel drops. No accidental IP leaks. Architectural, not a bolt-on.

Pay per GB

Prepaid credits. Residential from $3/GB, datacenter from $1/GB. No subscriptions, no minimums, no contracts.

Agent-native

AI agents, scripts, and automation use shellroute run to wrap any command with a proxy session. No code changes — proxy env vars are inherited automatically.

Quick example

terminal
$ npm install -g shellroute
$ shellroute login
  ✓ Logged in successfully

 shellroute · not connected · direct traffic
~  /connect US
  ✓ Connected to US (United States) — New IP: 45.12.67.89

 shellroute us · 45.12.67.89
~  curl https://ipinfo.io/ip
45.12.67.89
~  /exit

Built for agents

AI agents, browser automation, and scripts don't need an interactive shell. shellroute run wraps any command with a proxy session — starts, runs, and cleans up automatically.

agent / automation
# Agent checks its exit IP from the US
shellroute run --country US -- curl -s https://httpbin.org/ip
# → {"origin": "203.0.113.42"}

# Run a browser agent through Germany
shellroute run --country DE -- python browser_agent.py

# Parallel agents, each through a different country
shellroute run --country US -- python task.py --market us &
shellroute run --country JP -- python task.py --market jp &
wait

No code changes in the agent — proxy env vars are inherited automatically. See the full Agents & Automation guide.

Next steps