# Getting Started with StatesideIP US Proxies (2026)

> Set up US residential proxies in 6 steps: pay in crypto, copy credentials, add state, city, ZIP or ASN to the username, test with curl. No KYC; from $0.52/GB.

- URL: https://statesideip.com/guides/getting-started/
- Last updated: 2026-10-05
- Publisher: StatesideIP (https://statesideip.com)

From payment to your first targeted request: credentials, username syntax, curl tests over HTTP and SOCKS5, sticky sessions and fixes for common errors.

**Quick answer — How do I set up US residential proxies?**

To set up **StatesideIP** US residential proxies, buy a plan from $0.52/GB and copy your credentials. Add targeting such as `-country-us-state-ny` to the username. Then connect to `gw.statesideip.com` on port 7777 (HTTP) or 7778 (SOCKS5). No KYC — no ID, no selfie, no documents. Pay in crypto. A one-line curl test confirms the exit IP.

## What you need

| Attribute | Value |
| --- | --- |
| Plan | Any residential plan; 1 GB costs $1.50 (October 2026) |
| Gateway host | `gw.statesideip.com` |
| HTTP/HTTPS port | 7777 |
| SOCKS5 port | 7778 |
| Username format | `USERNAME-country-{cc}-state-{state}-city-{city}-zip-{zip}-asn-{asn}-session-{id}-ttl-{minutes}` |
| Sticky sessions | 1 to 120 minutes, set per session with the ttl parameter |
| Test endpoint | `https://api.ipify.org?format=json` (prints your exit IP) |
| Tools | curl, Python, Node.js or any tool that supports HTTP or SOCKS5 proxies |
| KYC | No KYC — no ID, no selfie, no documents. Pay in crypto. |

## How do I go from payment to the first request?

Six steps take you from an empty account to a working US IP.

1. **Buy a plan** — Pick a residential plan on the pricing page. The 1 GB plan at $1.50 is enough for a first test. Every plan, including the smallest, is paid from a $25 minimum top-up; the rest stays on your balance (never expires, non-refundable).
2. **Pay in crypto** — Choose BTC, USDT, USDC, ETH, LTC or SOL, then pay the invoice. See paying with crypto.
3. **Open the dashboard** — Credentials appear in your dashboard as soon as you buy a plan from your confirmed crypto balance. Copy your username and password.
4. **Build the username** — Start from your username and add targeting segments, such as -country-us-state-tx.
5. **Run a test** — Send one curl request to https://api.ipify.org?format=json and check the IP it prints.
6. **Point your tool at the gateway** — Use gw.statesideip.com with port 7777 or 7778 in your scraper, browser or script.

## Which username segments can I use?

Each segment in a StatesideIP username sets one option. Add only the ones you need, in the order of the format: `USERNAME-country-{cc}-state-{state}-city-{city}-zip-{zip}-asn-{asn}-session-{id}-ttl-{minutes}`.

| Segment | Sets | Example |
| --- | --- | --- |
| `country-{cc}` | Country, two letters | `country-us`, `country-ca`, `country-pr` |
| `state-{state}` | US state or Canadian province code | `state-fl`, `state-on`, `state-bc` |
| `city-{city}` | City, lowercase, underscores for spaces | `city-miami`, `city-san_antonio` |
| `zip-{zip}` | Five-digit US ZIP code | `zip-77006` (Montrose, Houston) |
| `asn-{asn}` | ISP network number, without "AS" | `asn-22773` (Cox) |
| `session-{id}` | Sticky-session ID of your choice | `session-run7` |
| `ttl-{minutes}` | Sticky-session length in minutes | `ttl-45` |

## How do I test the proxy with curl?

Run the HTTP test first, then the SOCKS5 test; both print the IP your request leaves from. Run each one twice: without a `session` segment, the IP should change. Use `--socks5-hostname` so DNS lookups also go through the proxy.

*curl over HTTP and SOCKS5*

```bash
# HTTP/HTTPS gateway: rotating US IP
curl -x http://gw.statesideip.com:7777 \
  -U "USERNAME-country-us:PASSWORD" \
  "https://api.ipify.org?format=json"

# SOCKS5 gateway: rotating IP in Florida
curl --socks5-hostname gw.statesideip.com:7778 \
  -U "USERNAME-country-us-state-fl:PASSWORD" \
  "https://api.ipify.org?format=json"
```

*Python (requests)*

```python
# pip install requests
import requests

proxy = "http://USERNAME-country-us-state-ca:PASSWORD@gw.statesideip.com:7777"
r = requests.get("https://api.ipify.org?format=json",
                 proxies={"http": proxy, "https": proxy}, timeout=30)
print(r.json())
```

*Node.js (undici)*

```javascript
// npm install undici
import { fetch, ProxyAgent } from "undici";

const agent = new ProxyAgent({
  uri: "http://gw.statesideip.com:7777",
  token: "Basic " + Buffer.from("USERNAME-country-us-state-ny:PASSWORD").toString("base64"),
});
const res = await fetch("https://api.ipify.org?format=json", { dispatcher: agent });
console.log(await res.json());
```

Respect robots.txt and each site's terms when you move from tests to real targets. The [Python guide](https://statesideip.com/guides/python-us-proxies/) goes further with Python examples.

## Rotating or sticky: which session type should I use?

Use rotating sessions for many independent requests, and sticky sessions for a flow that must keep one IP. Without a `session` segment, each request gets a new IP. With `session-{id}` and `ttl-{minutes}`, the IP stays for the time you set: 1 to 120 minutes, set per session with the ttl parameter.

- `USERNAME-country-us-state-ga-city-atlanta-session-cart01-ttl-20` keeps one Atlanta IP for 20 minutes.
- Change the session ID to get a different sticky IP.
- A home IP can go offline before the session ends, so add retries.

## How do I target a state, city, ZIP, ASN or Canadian province?

Change the segments after `country-`; the gateway, port and password stay the same.

- **State:** `USERNAME-country-us-state-oh` — Ohio.
- **City:** `USERNAME-country-us-state-co-city-denver` — Denver.
- **ZIP code:** `USERNAME-country-us-zip-98101` — downtown Seattle.
- **ASN:** `USERNAME-country-us-asn-5650` — Frontier's network.
- **Canadian province:** `USERNAME-country-ca-state-on` — Ontario. Canada uses the `state` segment for provinces.
- **Canadian city:** `USERNAME-country-ca-state-bc-city-vancouver` — Vancouver.

More examples: [ZIP code targeting](https://statesideip.com/targeting/zip-code/), [ASN targeting](https://statesideip.com/targeting/asn/) and the [US cities hub](https://statesideip.com/residential-proxies/united-states/cities/).

## What does a 407 Proxy Authentication Required error mean?

A 407 error means the gateway did not accept your username or password. Check for a typo in a segment, or a missing colon between username and password. In a proxy URL, special characters in the password may need URL-encoding. Copy the password again from the dashboard. If the credentials are right, check your balance and contact support.

## Why do requests time out?

Timeouts usually come from a filter that is too narrow, a slow home connection behind the IP, or a slow target. Widen a ZIP or ASN filter to the city or state. Set a client timeout of 30 seconds or more, and retry with a new IP. Sticky IPs can also drop when the home device goes offline.

## Why does the IP show the wrong location?

Geolocation databases disagree, so a correct IP can look wrong in one lookup tool. First check that the country, state and city segments match each other. City names need underscores, as in `city-san_antonio`. Then compare two or three lookup services, and test the target site itself.

## Getting started: frequently asked questions

### What do I need before I start?

You need a StatesideIP residential plan and the username and password from your dashboard. You also need a tool that supports HTTP or SOCKS5 proxies; curl is enough for a first test. The 1 GB plan at $1.50 covers a test of several locations. Every plan, including the smallest, is paid from a $25 minimum top-up; the rest stays on your balance (never expires, non-refundable). No ID or documents are needed to buy it.

### Which port should I use: 7777 or 7778?

Use port 7777 for HTTP and HTTPS clients, such as browsers, Python requests and most scrapers. Use port 7778 for SOCKS5, when a tool needs a socket-level proxy. Both ports take the same username and targeting segments, so you can switch without changing the login.

### Do targeting segments cost extra?

No. State, city, ZIP and ASN segments are included on every StatesideIP residential plan, as of October 2026. Plans run from $1.50 for 1 GB to $0.52/GB at volume, and only traffic is billed. Every plan, including the smallest, is paid from a $25 minimum top-up; the rest stays on your balance (never expires, non-refundable). Residential traffic does not expire, so a test balance stays available for later work.

### Can I use the same credentials for several projects?

You can, but sub-users keep projects apart. Plans from 10 GB include sub-users for each project, and the 100 GB plan adds usage stats per sub-user. Each project then gets its own login and its own traffic total, which makes costs easier to track.

### How do I set up a Canadian IP?

Change the country segment to `ca` and use the `state` segment for the province. For example, `USERNAME-country-ca-state-qc-city-montreal` gives a Montreal IP. StatesideIP covers all 10 Canadian provinces with province, city and ASN targeting. ZIP targeting applies to five-digit US ZIP codes only.

### What should I do if nothing works?

Run the curl test from this guide with only `-country-us` added, to rule out targeting errors. If it still fails, copy the exact error message and the time, and email support@statesideip.com. Email replies within 12 hours, 7 days a week. Never send your password in the email.

**Ready for your first US IP?** Residential proxies from $0.52/GB, with state, city, ZIP and ASN targeting. No KYC — no ID, no selfie, no documents. Pay in crypto. [Get US residential proxies — from $0.52/GB](https://statesideip.com/pricing/) · [Python guide](https://statesideip.com/guides/python-us-proxies/)

---

StatesideIP: StatesideIP is a US and Canada proxy provider: residential IPs with state, city, ZIP and ASN targeting, plus dedicated T-Mobile, AT&T and Verizon 4G/5G mobile ports. No KYC — no ID, no selfie, no documents. Pay in crypto.