Route a Steel browser session through residential proxies or bring your own proxy (BYOP)
domain: docs.steel.dev · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Steel-managed residential proxies: create the session with useProxy: true — traffic routes through a US-based residential IP by default
Geo-targeting (Steel-managed): pass a geolocation object inside useProxy, e.g. useProxy: { geolocation: { country: 'US', state: 'NY' } } or { city: 'LOS_ANGELES' } — 200+ countries via Alpha-2 codes, US states, and major cities
BYOP: pass your own proxy server instead: useProxy: { server: 'http://username:password@proxy.example.com:8080' }
Supported BYOP formats: http://, https://, and socks5:// URLs with embedded username:password
All traffic in the session then routes through the proxy — no changes needed in your Playwright/Puppeteer code
Steel-managed residential proxy bandwidth is billed per GB: $10/GB on Launch, $6/GB on Scale; Launch also requires a $10 paid-balance account verification before proxies can be enabled
Default (useProxy omitted/false) uses Steel's own egress at no proxy charge — fine for sites without anti-bot measures
Proxy settings are fixed at session creation; to change proxy or geo, release the session and create a new one
Geo-targeting works only with Steel-managed proxies; BYOP location is wherever your proxy exits
Give your agent this knowledge — and 16,400+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?