Egress

Chaser sessions route their traffic through residential proxies. The proxy IP matches the session’s profile — a mobile profile egresses through a mobile residential IP, and the IP’s ASN and geography are consistent with the claimed device.

How it works

You don’t configure proxies. You don’t choose proxy endpoints. The session’s traffic is automatically routed through the residential proxy network. The proxy is included in the $5/GB price — no separate proxy fee, no per-GB surcharge, no proxy configuration in your code.

Checking the egress IP

To see what IP a session is egressing from, visit a service like https://httpbin.org/ip from within the session, or check the session resource:

$
curl -s "https://api.chaser.sh/v1/sessions/$SESSION_ID" \
>
  -H "Authorization: Bearer $CHASER_KEY" | jq '{proxy_ip, proxy_region}'

The proxy_ip and proxy_region fields are populated once the session’s proxy connection is established.