Everything the proxy API actually does
No hidden internals — this is what a session request controls, and what the control plane does with it before your traffic ever leaves.
Rotating or sticky, your choice per request
Rotating sessions
A new exit IP on every request. Built for high-volume scraping and anything where request-to-request continuity doesn't matter.
Sticky sessions
The same exit IP held for a configurable window — 10 minutes by default. For checkout flows, multi-step forms, anything that needs a consistent identity mid-flow.
Country and city, as connection parameters
Pass country-us or, where node density allows, city-chicago directly on the session request — no separate endpoint per region to integrate against.
Broad targeting
Works everywhere there's contributor density — the common case for most integrations.
Precise targeting
Available where node density supports it. Falls back cleanly to country-level if a city has no live capacity.
No preference
Skip targeting params entirely and get whatever healthy node the router picks — the fastest way to get moving.
Nodes are scored, not just up or down
Every node carries a rolling reputation score the router weighs before assigning it a session — not a binary online/offline flag.
Uptime consistency
Nodes that flap between connected and dropped get deprioritized before they're ever fully excluded.
Complaint rate
Abuse reports and blocklist hits against sessions routed through a node pull its score down.
Measured latency
Scored against our own reference probes — not self-reported by the node.
A blocklist that runs before a connection opens
Session-level audit logs (account, node, destination category, timestamp) exist to answer abuse reports — retained on a fixed window, not indefinitely.