Quickstart

1. Create an account

Open the register page and click Generate account. You get three secrets shown once:

whisker key:  whisker-DLDI-ZF6C-RCCT-3FLJ-...   (sign in at /account)
collar tag:   cat-XS73LMPQOFK762Q4              (proxy username base)
pawprint:     a14c2f9f5068d0ddd2f50c39bad4bfdd  (proxy password, life 1)

Save the whisker key — it owns the account and is never shown again after your first visit to the dashboard. The collar and pawprint are what you put in proxy clients. See Authentication.

2. Fund it

Top up with any enabled coin (Bitcoin, Monero, Litecoin, Ethereum, and others when configured). Traffic is credited automatically once the transaction confirms (see Payments). Until then the account has no traffic. An unfunded account is deleted after 24 hours.

3. Make a request

Point any proxy-aware client at the gateway using your collar as the username and your pawprint as the password. The gateway auto-detects the protocol, so the same host/port works for SOCKS and HTTP:

# HTTP(S)
curl -x http://cat-XS73LMPQOFK762Q4:PAWPRINT@socks.cat:1337 https://example.com

# SOCKS5
curl -x socks5h://cat-XS73LMPQOFK762Q4:PAWPRINT@socks.cat:1337 https://example.com

Need another pawprint later? Use Account settings to derive one.

4. Choose where you exit (optional)

Append routing tags to your collar to pick a country, city, ISP, or exit type:

curl -x socks5h://cat-XS73LMPQOFK762Q4-country-us-type-residential:PAWPRINT@socks.cat:1337 https://api.ipify.org

Browse codes at /locations or use the endpoint builder.

See Protocols & examples for browser, Python and Node snippets, Routing for location selection, and Authentication for credentials and IP-based auth.