Dynamic residential

Per-gigabyte residential proxies with country-to-city targeting, operator ASN and OS targeting, and 1–120 minute sticky sessions.

The most capable of the four lines, and the only one that supports city-level targeting, operator ASN and OS targeting, and sticky session options. Billed per gigabyte, which suits workloads with many requests but small payloads.

Billing and packages

Unit: GB
Two purchase shapes:
- Fixed packages (package) — preset gigabyte tiers
- Custom volume (custom) — you name the number of gigabytes; the code caps at 1,000,000 GB, with the real range bounded by each product's minGb / maxGb
Quote validity: 5 minutes by default, shortened if a promotion or the product's delisting comes sooner. An expired quote must be re-requested.
Balance: purchases accumulate into the account's traffic pool. There is no code-level automatic expiry or forfeiture in the current implementation.

Supported targeting options

This line supports every targeting dimension, appended to the username in this order:

Option	Values	Notes
`country`	Two uppercase letters	Must be uppercase; `us` is rejected
`state` or `region`	1–100 bytes	Fully equivalent keys; cannot be used together
`city`	1–100 bytes	Exact match, case-sensitive
`asn`	Number, optional `AS` prefix	This is how you target an operator; `64512`, `AS64512`, `as64512` all work
`os`	`windows`, `android`, `ios`, `mac`	Choose the proxy exit device’s operating system; Any leaves it unrestricted
`session`	1–64 bytes, `[A-Za-z0-9.-]`	Must appear with `time`
`time`	Integer 1–120	Minutes; must appear with `session`

Full escaping rules, ordering constraints and failure examples are in Username option reference.

shell

# Los Angeles + 30 minutes sticky
curl -x 'http://USERNAME-country-US-state-California-city-Los%20Angeles-session-job1-time-30:PASSWORD@GATEWAY_HOST:58971' \
  https://api.ipify.org

# Operator targeting (Comcast's AS7922). asn can't be combined with state or city
curl -x 'http://USERNAME-country-US-asn-7922-session-job1-time-30:PASSWORD@GATEWAY_HOST:58971' \
  https://api.ipify.org

OS targeting works on its own or with location targeting. For example, request a US iOS exit:

shell

curl -x 'http://USERNAME-country-US-os-ios:PASSWORD@GATEWAY_HOST:58971' \
  https://api.ipify.org

Real-world limits on targeting

Valid targeting options still require an available matching IP. Keep these limits in mind:

State and city targeting depends on whether that country is opened down to that level. City targeting in practice requires country and state to be supplied too.
Available ASN options are listed in the console catalogue.
Selecting an operating system restricts results to proxy IPs matching that system.
Combining ASN with state or city may be unavailable; use these filters separately.
Session duration can be set from 1 to 120 minutes.

When no available IP matches the selected filters, the request returns HTTP 503 service_unavailable (SOCKS5 reply 0x01). Remove filters one at a time and retry.

Sessions and rotation

With session + time: the same proxy account, session value and filters keep the same exit IP for time minutes. An exit device going offline can affect IP availability.

Without session: every new TCP connection receives a newly assigned exit IP, which may repeat a previous result.

The same session value with different operating systems uses separate sessions. Sticky sessions do not guarantee a permanently fixed IP. Use static residential when you need a long-term fixed IP.

More detail in Sticky sessions and rotation.

Metering

Only payload bytes successfully relayed in either direction are counted; handshakes are free.

Counted: everything after the CONNECT tunnel is established (TLS records, HTTP headers, bodies), the reconstructed request headers in ordinary forward mode, upload plus download.

Not counted: the CONNECT request headers you send to the gateway, the 200 Connection Established reply, SOCKS5 greeting and authentication, the gateway-to-exit handshake, TCP/IP packet headers.

Billed traffic is then multiplied by a product multiplier and floored after accumulation. Details in Traffic accounting.

Where it fits

Good fit

Web scraping, price comparison, SERP collection
Verification work that needs city- or operator-level precision
Short multi-step flows that need stickiness (log in → paginate → submit)

Poor fit

Large downloads and video streams — per-gigabyte gets expensive; use unlimited residential
A fixed IP for months — use static residential
Low latency with no need for residential attribution — use datacenter

Programmatic extraction

Besides composing usernames directly, the Extract API hands back a batch of ip:port entries for passwordless access via source-IP whitelisting. That suits setups where region and session configuration live on the server and clients only receive a list of ports.

OS targeting is currently available only for username/password access, not the Extract API. Choose Windows, Android, iOS, or macOS in the generator; Any omits the os option.