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.
shellroute login, then /connect US. That shell now has its own US route. Open another shellroute session for another country; the rest of your machine stays direct.
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
Each shellroute session gets its own route. Other terminals, your normal browser, and system processes keep their existing connections.
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
Agents can invoke shellroute run for a country-specific command. Shellroute opens the session, runs the command, and cleans up when it exits.
Quick example
$ 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
~ ❯ /exitBuilt for agents
Agents, browser automation, and scripts can use shellroute run without opening an interactive shell. Shellroute starts the session, runs the command, and cleans up when it exits.
# 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 &
waitGive each agent command its own shellroute session. See the full Agents & Automation guide.