Four billing models

Residential proxy pricing, billed the way you actually run

Traffic from $0.8/GB, bandwidth from $32/day for 100Mbps, short-term static from $0.08 per IP-day, long-term native from $3.8 per IP-month. Unit prices step down with volume, and traffic never expires.

4 billing models

Which plan fits

One network underneath all four. What changes is how you are billed and how long a session holds. Match the shape of the workload first, then compare rates.

Rotating Residential · Traffic

Billed per GB

$0.8

/GB and up

The tier that does not punish a quiet month. Traffic sits in your balance until you spend it, so a slow week costs nothing and a spike needs no new contract.

Includes

  • 90M+ residential IPs across 195 countries and regions
  • Rotation set from 1 to 360 minutes, sticky sessions up to 120
  • Targeting down to city, state or ASN
  • HTTP(S) and SOCKS5, with no concurrency cap
  • Traffic never expires, and sub-accounts split the quota

Rotating Residential · Bandwidth

Billed per Mbps, unmetered

$32

/day · 100Mbps

The more you push through it, the better it prices. You buy bandwidth and the bytes are not metered, so a pipeline that runs around the clock has a cost you can state in advance.

Includes

  • Unmetered traffic, billed per Mbps per day
  • No concurrency cap, 99.9% request success
  • The same 90M+ residential pool as the traffic tier
  • Choose a bandwidth tier or a port-count tier
  • under 0.6s average response, 99.9% uptime

Static Residential · Short-term

Billed per IP per day

$0.08

/IP/day and up

When the identity only has to hold for a few days, paying by the day beats paying by the month. Release it when the job ends and nothing keeps billing.

Includes

  • Billed per IP per day — you pay for the days you hold it
  • The exit address stays fixed for the whole session
  • Unmetered bandwidth, with no separate traffic charge
  • Pull them by API, user:pass auth or IP allowlist
  • Extract in bulk by country and city

Static Residential · Long-term

Native ISP, dedicated monthly

$3.8

/IP/month and up

The only tier for accounts you intend to keep. A native-ISP ASN, dedicated to one customer, and renewal holds the same address — so the platform is never asked to re-verify a stranger.

Includes

  • A real native-broadband ASN that reverse-lookups as residential
  • Dedicated to you, never shared with another customer
  • The address stays put, and renewal keeps it
  • City and state targeting, with carrier choice in 33 markets
  • Unmetered bandwidth over both HTTP(S) and SOCKS5

4 × 4

Volume pricing

The unit price falls as commitment rises. These are the common tiers — larger volumes are quoted directly.

Rotating Residential · Traffic

Volume Unit price
10 GB $1.2/GB
50 GB $1.0/GB
200 GB $0.9/GB
1 TB $0.8/GB

Rotating Residential · Bandwidth

Volume Unit price
100 Mbps $0.32/Mbps/day
200 Mbps $0.30/Mbps/day
500 Mbps $0.28/Mbps/day
1 Gbps $0.26/Mbps/day

Static Residential · Short-term

Volume Unit price
10 IP $0.12/IP/day
50 IP $0.10/IP/day
200 IP $0.09/IP/day
1,000 IP $0.08/IP/day

Static Residential · Long-term

Volume Unit price
5 IP $5.5/IP/mo
20 IP $4.8/IP/mo
100 IP $4.2/IP/mo
500 IP $3.8/IP/mo

About these prices

Every figure here is an entry rate that steps down with volume, and prices exclude tax. Traffic plans have no expiry — the balance stays in your account until you use it. Static IPs bill for the term you buy, and renewing keeps the same address rather than issuing a new one. For enterprise volume, custom payment terms or an IEPL quote, email support@zapip.net.

FAQ

Pricing questions

How much does a residential proxy cost per GB?

Rotating residential traffic runs $1.2/GB at 10 GB, $1.0 at 50 GB, $0.9 at 200 GB and $0.8 from 1 TB up. If the workload runs continuously and you want the effective per-GB number lower still, the bandwidth tier is the better instrument: 100Mbps for $32/day with the bytes unmetered lands far below any per-GB plan once you actually saturate the link.

How does volume pricing work — do I have to commit up front?

The unit price is set by the size of the top-up, applies the moment it lands, and carries no annual contract or monthly minimum. Traffic already in the account is not repriced when you later buy a cheaper tier, so there is no reason to over-buy early — start at real usage and step up when the volume is actually there. Sustained enterprise volume is quoted separately.

Does unused traffic expire, and can I get a refund?

Traffic plans have no expiry date — the balance stays in the account until you spend it. On refunds: where the service is technically unusable, you can claim the unconsumed portion within three days of purchase. Traffic already consumed is not refundable, and orders paid in cryptocurrency are not refundable at all. Static IPs bill for the term you bought; releasing one early does not produce a pro-rata credit.

Cheap residential proxies advertise half this price. What is the difference?

Three places, usually. Sourcing: cheap pools mix in nodes the household never knowingly consented to, which makes the chain unauditable and whole ranges liable to be blocked at once — ZapIP sources through KYC-authorised channels that can be traced. Purity: pools without continuous reputation checks sell you IPs that are already flagged, and you pay full price for them. And failure rate — a unit price 30% lower with success falling from 99.9% to 80% costs more per usable record, not less. Run a real batch and compare cost per successful request rather than the number on the pricing page.

What payment methods do you accept, and can I test small before scaling?

Credit card, Alipay, bank transfer and USDT are supported, balances credit immediately, and usage breaks down by sub-account in the console. Buy the smallest tier first and run your actual workload against your actual targets — success rate, response time and block behaviour tell you more than any benchmark we could publish — then scale. An engineer works with you through the integration. One caution: crypto payments are non-refundable, so use a refundable method while you are still testing.

Get one request working. Scale after that.

Test before you commit, with an engineer on your integration.