Products
Seven products, documented to the same standard
Each product below is distinct, with its own economics and its own SLA. They share one gateway, one credential format, and one chain-of-custody standard, so moving a workload between them is a parameter change.
Residential
Consented peer addresses across 195 countries, billed by traffic.
What it is
Addresses assigned by consumer ISPs to real households, reached through peers who opted in to share bandwidth and are compensated for it. Every peer arrives through a partner application carrying a disclosure we have reviewed ourselves. Rotation is per request or sticky for up to 60 minutes, and a session can be pinned to a country, region, city, or ASN.
Use cases
- Price and assortment monitoring on retail sites that segment by geography
- Ad verification and brand-safety sampling from consumer vantage points
- Search result and marketplace ranking measurement
- Availability testing for consumer-facing products across markets
Key specifications
- Pool size
- 38M+ addresses
- Coverage
- 195 countries, 4,100+ cities
- Targeting
- Country, region, city, ASN
- Session control
- Rotating or sticky to 60 min
- Protocols
- HTTP, HTTPS, SOCKS5
- Auth
- User:pass or IP allowlist
- Concurrency
- Unmetered
- Billing unit
- Per GB, rounded to the MB
Service level
- Availability
- 99.9% monthly gateway availability
- Quality target
- 99.2% median request success across the pool
- Support
- Named engineer, 4-hour first response
- Service credits
- 10% of monthly spend per 0.1% below target, to 50%
Service credits are applied automatically against the following invoice. You do not have to notice the breach to be paid for it.
ISP
Static addresses issued by consumer ISPs, hosted on our hardware.
What it is
Addresses leased directly from consumer internet providers under commercial contracts and announced from our own racks. They present as residential to the networks you reach while behaving like datacenter capacity: fixed, fast, and yours for the month. No peer devices are involved, so there is no consent question to answer — only a contract to show you.
Use cases
- Long-lived sessions that must not change address mid-workflow
- Account operations where a stable origin is a requirement
- High-throughput collection that still needs consumer-ISP reputation
- Workloads a third party must allowlist in advance
Published rate
entry rate — volume floor · min 50 addresses
Key specifications
- Assignment
- Static, dedicated to one customer
- Coverage
- 31 countries, 9 tier-1 ISPs
- Throughput
- 1 Gbps per address, unmetered
- Latency
- Median 41 ms to regional targets
- Subnet spread
- Max 64 addresses per /24 by default
- Protocols
- HTTP, HTTPS, SOCKS5
- Minimum
- 50 addresses
- Billing unit
- Per address, per month
Service level
- Availability
- 99.99% monthly address availability
- Quality target
- Replacement within 4 hours for any flagged address
- Support
- Named engineer, 1-hour first response
- Service credits
- Pro-rata refund plus 20% for any address below target
Service credits are applied automatically against the following invoice. You do not have to notice the breach to be paid for it.
Datacenter
Dedicated addresses in our own ranges, announced from our own ASN.
What it is
Addresses from ranges we hold registrations for, announced from our ASN in facilities we contract directly. Nothing is resold, so provenance is a registry lookup rather than a trust exercise. Dedicated by default: an address assigned to you is used by no one else for as long as you hold it.
Use cases
- High-volume collection where throughput matters more than origin type
- Internal load, uptime, and regional performance testing
- API integrations that require a fixed, allowlistable origin
- Cost-sensitive workloads that do not need consumer-ISP reputation
Key specifications
- Assignment
- Dedicated, never shared
- Ranges
- Registered to us, announced from our ASN
- Coverage
- 24 countries, 39 facilities
- Throughput
- 10 Gbps per address, unmetered
- Latency
- Median 9 ms to regional targets
- Subnet spread
- Configurable, /24 diversity on request
- Protocols
- HTTP, HTTPS, SOCKS5
- Billing unit
- Per address, per month
Service level
- Availability
- 99.99% monthly address availability
- Quality target
- Replacement within 1 hour for any flagged address
- Support
- Named engineer, 1-hour first response
- Service credits
- Pro-rata refund plus 20% for any address below target
Service credits are applied automatically against the following invoice. You do not have to notice the breach to be paid for it.
Mobile
Carrier-assigned addresses on 3G, 4G, and 5G, billed by traffic.
What it is
Addresses assigned by mobile network operators to real handsets and modems, reached through the same consented-peer programme as our residential pool plus a fleet of modems we operate ourselves. Carrier-grade NAT means these addresses sit alongside ordinary subscriber traffic, which is exactly why they carry the reputation they do.
Use cases
- Mobile ad verification and creative rendering checks
- App store ranking and availability measurement by market
- Testing mobile-first products under real carrier conditions
- Collection from targets that treat mobile origins differently
Key specifications
- Pool size
- 2.4M+ addresses
- Coverage
- 84 countries, 310+ carriers
- Targeting
- Country, carrier, connection type
- Session control
- Rotating or sticky to 30 min
- Protocols
- HTTP, HTTPS, SOCKS5
- Auth
- User:pass or IP allowlist
- Concurrency
- Unmetered
- Billing unit
- Per GB, rounded to the MB
Service level
- Availability
- 99.9% monthly gateway availability
- Quality target
- 98.7% median request success across the pool
- Support
- Named engineer, 4-hour first response
- Service credits
- 10% of monthly spend per 0.1% below target, to 50%
Service credits are applied automatically against the following invoice. You do not have to notice the breach to be paid for it.
Scraper API
One call per page. We hold the addresses; you get the HTML.
What it is
A request-metered endpoint that fetches a URL and returns the response body. Rotation, retries and exit selection happen on our side against the same pools sold above, so there is no gateway to configure, no allowlist to maintain and no address inventory to hold. The unit you buy is a page that came back, and the meter counts requests rather than bytes.
Use cases
- Scheduled collection from catalogue and listing pages
- Programmes too small to justify operating a pool
- Teams without an engineer to own rotation and retry policy
- Pipelines that want HTML in and nothing else to reason about
Key specifications
- Interface
- HTTPS API, one call per page
- Rotation
- Ours, per request
- Targeting
- Country
- Session control
- Not applicable — no address is held
- Protocols
- HTTPS
- Auth
- API key
- Concurrency
- Unmetered
- Billing unit
- Per 1,000 requests, stepped in thousands
Service level
- Availability
- 99.9% monthly endpoint availability
- Quality target
- 97.5% median fetch success across measured targets
- Support
- Named engineer, 4-hour first response
- Service credits
- 10% of monthly spend per 0.1% below target, to 50%
Service credits are applied automatically against the following invoice. You do not have to notice the breach to be paid for it.
SERP API
Search results, parsed into structure, billed by the request.
What it is
The Scraper API pointed at search engines, returning parsed results rather than raw markup. Locale, language and device are parameters on the call, so a rank measured from Munich on a phone is one request rather than a session to arrange. Billed on the same ladder as the Scraper API because it is the same meter.
Use cases
- Rank and visibility tracking across markets and devices
- Share-of-voice measurement against a competitor set
- Local pack and map result monitoring by city
- Feeding a reporting pipeline that wants rows, not HTML
Key specifications
- Interface
- HTTPS API, one call per query
- Rotation
- Ours, per request
- Targeting
- Country, language, device
- Session control
- Not applicable — no address is held
- Protocols
- HTTPS
- Auth
- API key
- Concurrency
- Unmetered
- Billing unit
- Per 1,000 requests, stepped in thousands
Service level
- Availability
- 99.9% monthly endpoint availability
- Quality target
- 98.0% median parse success across measured engines
- Support
- Named engineer, 4-hour first response
- Service credits
- 10% of monthly spend per 0.1% below target, to 50%
Service credits are applied automatically against the following invoice. You do not have to notice the breach to be paid for it.
Unblocker API
The Scraper API that keeps going until a page comes back.
What it is
The same interface as the Scraper API, with rotation, backoff and challenge handling applied until the target returns real content. It is priced above the scraper for exactly that reason: a request buys persistence rather than a single attempt, and the work behind a retried fetch is not free. Use it where a plain fetch already failed, and not before.
Use cases
- Targets that answer with an interstitial rather than content
- Sources where a plain fetch succeeds only intermittently
- Collection that would otherwise be weeks of hand-tuning
- Programmes already attempted on the Scraper API without success
Key specifications
- Interface
- HTTPS API, one call per page
- Rotation
- Ours, with retries until success
- Targeting
- Country
- Session control
- Not applicable — no address is held
- Protocols
- HTTPS
- Auth
- API key
- Concurrency
- Unmetered
- Billing unit
- Per 1,000 requests, stepped in thousands
Service level
- Availability
- 99.9% monthly endpoint availability
- Quality target
- 99.1% median fetch success across measured targets
- Support
- Named engineer, 1-hour first response
- Service credits
- 10% of monthly spend per 0.1% below target, to 50%
Service credits are applied automatically against the following invoice. You do not have to notice the breach to be paid for it.
Not sure which network fits the job?
Describe the target, the volume, and the constraint you are working against. We will tell you which product to use, including when the answer is the cheaper one.
One business day, from a named engineer.