Residential setup

Residential endpoints route your traffic through real residential IPs. Point your client at the gateway and authenticate with your collar and pawprint.

Endpoint

socks.cat:1337

The gateway auto-detects SOCKS5/SOCKS4/HTTP/HTTPS, so one endpoint serves every client type.

Sticky vs. rotating sessions

• Rotating (default) — each new connection may exit from a different IP. Good for broad scraping.
• Sticky — keep the same exit IP by adding -session-<id> to the collar. The id is arbitrary; reuse it to keep the IP, change it to rotate. Optionally add -lifetime-<minutes> to cap how long the pin lasts. This is not the session id.

# Rotating
curl -x socks5h://COLLAR:PAWPRINT@socks.cat:1337 https://api.ipify.org

# Sticky (same exit until you change "ab12")
curl -x socks5h://COLLAR-session-ab12:PAWPRINT@socks.cat:1337 https://api.ipify.org

Pin type-residential to stay on residential exits:

curl -x socks5h://COLLAR-type-residential-session-ab12:PAWPRINT@socks.cat:1337 https://api.ipify.org

Geo-targeting

Browse codes at /locations, use the endpoint builder, or append routing tags to your collar — country, state, city, isp, type — or set a default on your account page:

# residential exit in the US on Comcast
curl -x socks5h://COLLAR-country-us-isp-comcast-type-residential:PAWPRINT@socks.cat:1337 https://api.ipify.org

Tips

• Prefer socks5h:// (note the h) so DNS resolves at the exit, not locally.
• Set generous timeouts; residential hops add latency.
• Traffic is metered in bytes against your prepaid quota — see Payments.