200 million exits,
already deployed.
Rotating residential proxies across 195+ countries with per-request geo targeting down to the ISP. Incumbents had to buy their network. Ours is already deployed, and it is paid to participate.
[ WHY RESIDENTIAL COSTS WHAT IT COSTS ]
You are paying off somebody else's acquisition bill
Residential proxy providers do not own homes. They rent access — through SDKs quietly embedded in free apps, through affiliate networks, through acquisitions of the companies that did the embedding. That supply chain is expensive and legally fragile, and the price you pay is what servicing it costs.
Bandwidth acquired through intermediaries, marked up at every hop.
The person carrying your traffic often never knowingly agreed to it.
Per-port and per-session charges on top of bandwidth, for no marginal cost.
Upfront commitments before you can evaluate whether it even works.
[ TARGETING ]
Country, state, city, carrier — per request
One endpoint takes a geo string and gives you an exit that matches it. No separate gateway per region, no pool to provision in advance, no ticket to open. Change the header and the next request comes out of a different continent.
- COUNTRYUnited States41.2M exits
- STATETexas3.1M exits
- CITYAustin412K exits
- ISPSpectrum88K exits
geo: US/tx/austin/spectrum
session: sticky-10m # or: rotate[ WHAT YOU GET ]
Built to be the boring part of your pipeline
Open as many simultaneous connections as your infrastructure can drive. There is no per-port fee, no session cap and no thread limit to negotiate for.
A dead exit is retried on a fresh node inside the gateway, transparently. You see a 200 and a slightly longer response time, not a 502 to handle yourself.
Every node installed the software deliberately, set its own cap and is paid per gigabyte. When procurement asks where the bandwidth comes from, there is an answer.
Drop-in with whatever you already run — Scrapy, Playwright, Puppeteer, curl, or your own client. Standard proxy auth, standard everything.
Exit IP, carrier, country, timing breakdown and cost returned on every call. Usage streams to a webhook so billing never surprises you.
We bill on byte counters, not on request records. The URLs you fetch are not stored, which means they cannot be leaked, sold or subpoenaed.
[ INTEGRATION ]
Live in about four minutes
Point your existing client at p.ice.io, add a geo header, and you are done. No SDK required, no dashboard to configure first, and nothing about your pipeline has to change.
# any HTTP client, standard proxy auth
curl -x "http://user:key@p.ice.io:9000" \
-H "x-ion-geo: US/tx/austin/spectrum" \
-H "x-ion-session: rotate" \
https://market.example/prices
200 OK
x-ion-exit: 24.28.119.60
x-ion-isp: Spectrum
x-ion-ms: 62
x-ion-cost: 0.00021 USD
# settings.py — nothing else changes
DOWNLOADER_MIDDLEWARES = {
"scrapy.downloadermiddlewares.httpproxy"
".HttpProxyMiddleware": 750,
}
ION_PROXY = "http://user:key@p.ice.io:9000"
DEFAULT_REQUEST_HEADERS = {
"x-ion-geo": "DE/berlin/telekom",
"x-ion-session": "sticky-10m",
}
# unlimited concurrency — tune to your box
CONCURRENT_REQUESTS = 512
{
"status": 200,
"exit": {
"type": "residential",
"ip": "24.28.119.60",
"isp": "Spectrum",
"cc": "US", "city": "Austin"
},
"timing": { "connect": 21, "total": 62 },
"bytes": 178432,
"cost_usd": 0.00021,
"retries": 0,
"logs_retained": 0
}
[ COMPARE ]
Line by line against the incumbents
| Feature comparison | Enterprise providers | Budget resellers | ION Proxies |
|---|---|---|---|
| Pool size | 10M – 72M | 1M – 10M | 200M+ |
| Supply consent | SDK-bundled | Resold, opaque | Opt-in, paid per GB |
| Targeting depth | City / ASN | Country | Country → state → city → ISP |
| Concurrency limits | Per-port fees | Thread caps | Unlimited |
| Minimum commitment | Required | Often | None |
| Request logs retained | Yes | Yes | None |
| Agent-native payment | No | No | x402 per request |
[ USE CASES ]
What teams run through it
Retail and travel pricing is geo-personalised. Exit inside the market you're measuring and you get the number a real customer sees, not the one shown to a datacenter.
Search and marketplace pages rate-limit datacenter ranges within minutes. Residential exits with per-request rotation keep the crawl running.
Confirm creative, placement and geo-targeting from inside the market — down to the specific carrier the campaign was bought against.
Grey-market listings are hidden from anything that looks automated. A household exit sees the storefront as a local shopper does.
Unlimited concurrency and 200M exits make large corpus collection a throughput problem rather than a blocking problem.
Verify CDN behaviour, geo-routing and localisation from the exact city and carrier your users are actually on.
[ FAQ ]
Questions people actually ask
The corner everyone else cuts is where the supply comes from — and paying for it properly through intermediaries is the expensive part. ION pays households directly, per gigabyte, with no acquisition cost, no affiliate layer and no SDK vendor taking a margin.
Every node runs software the operator installed deliberately, having set a bandwidth cap and reviewed what the network carries. They can see every request routed through them and switch off instantly. There is no bundled SDK and no silent participation — which is exactly the part of this industry that gets providers into trouble.
Payment per request makes bulk abuse expensive rather than free. On top of that, abusive destination categories are blocked at the gateway, node operators can refuse categories themselves, and rate limits apply per account. Accounts that trip them are cut off rather than warned.
No. Billing runs on byte counters, not request records, so target URLs are never written down. The per-request detail you get back is generated in the response and not retained on our side.
99.2% across the network on general traffic. On aggressively defended targets it depends far more on your own request shaping than on the exits — which is why there's a free trial gigabyte: run it against your actual targets before you commit to anything.
Yes — that's what ION Agents is. One x402 micropayment per request, settled on-chain, no signup and no API key to leak. Same network, same exits, different front door.
Neither. Pay for the bytes you move, stop whenever. There is no minimum and no commitment.
[ 05 · PROXIES ]
Run your first gigabyte free
API access and a trial gigabyte for teams that join before launch.
Keys issued in join order · no sales call required