Skip to main content
Route the browser’s egress through your own proxy by setting network.proxy_url. Reach for it when the target site blocks datacenter IPs or geofences by region, or when a run needs traffic from a specific network.
FieldTypeDefaultDescription
network.proxy_urlstring | nullnullBring-your-own proxy URL for browser egress, with any credentials inline: http://user:pass@host:port. HTTP, HTTPS, and SOCKS schemes are accepted. Treat the value as a secret.
The proxy is applied only when the platform provisions a new browser session, and only on headful chromium runners. It cannot be combined with session_id, which attaches to an already-provisioned session. Create a catalog browser environment that routes through a proxy: 
curl -X POST https://agp.eu.hcompany.ai/api/v2/environments \
  -H "Authorization: Bearer $HAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "proxy-browser",
    "kind": "web",
    "network": {"proxy_url": "http://user:pass@proxy.example.com:8080"}
  }'