Browser API
Residential proxies in Steel
Steel runs headless browsers in the cloud for agents and scrapers. Its bring-your-own-proxy option works on every plan: hand it our gateway in useProxy.server and each session browses from a home IP in the country you choose.
- Host
- via.proxies.vision
- Ports
- 9000 rotating · 10000 sticky
- Same IP for
- up to 24 hours
- Price
- $1/GB, never expire
The code
Steel reads the login from the proxy URL. Replace USER and PASS with your login from the dashboard. In Python the field is use_proxy.
import Steel from "steel-sdk";
const client = new Steel();
const session = await client.sessions.create({
useProxy: {
server: "http://USER-country-us-session-run1-lifetime-30:PASS@via.proxies.vision:10000",
},
});Set it up in Steel
As in Steel's documentation today.
01
Get your login
Sign up and copy your proxy username and password from the dashboard.
02
Build the proxy URL
http://username:password@via.proxies.vision:port. Port 9000 rotates per connection, 10000 keeps a session's IP.
03
Create the session
Pass the URL as useProxy.server (use_proxy in Python) when you create the Steel session.
04
One session name per run
Give each browser session its own session name so parallel runs don't share an IP.
Questions
- Rotating or sticky?
- Port 9000 gives every new connection a new home IP, good for crawling many pages. For a logged-in flow that has to keep one IP, put a session in the username (USER-session-job1-lifetime-30) and use port 10000; the same session name keeps the same exit for its lifetime.
- Can I use SOCKS5?
- Yes, Steel accepts http, https and socks5 proxy URLs. Our SOCKS5 ports are 11000 (rotating) and 12000 (sticky).
- What does it cost?
- $1 per GB of traffic, whatever the country, city or network. No subscription, and unused bandwidth never expires. An agent that loads full pages uses more than one fetching HTML, so block images and media where the task allows it.
