Network
What kind of proxy this actually is
Rotating datacenter HTTPS egress, reached through a JSON API rather than a host:port proxy string. Knowing which of those words apply to you is most of the buying decision, so here they are up front.
What we do not offer
No residential addresses, no mobile carrier addresses, and no SOCKS5. If a target blocks datacenter address ranges, a datacenter proxy does not solve it, and no amount of rotation within our range changes the answer. Search engines are the clearest example: they serve a JavaScript challenge to datacenter addresses, which is why we withdrew our search-results endpoint instead of selling one that returns nothing.
Datacenter, and honest about it
Our addresses belong to AWS ranges, because our nodes are EC2 instances we run. That makes them fast, stable and cheap to operate, and it makes them recognisable as datacenter addresses to any site that checks.
For the large majority of targets — public APIs, documentation, product pages, feeds, most e-commerce catalogues — this is exactly the right tool. For targets that specifically block cloud ranges, it is the wrong one, and we would rather you knew that now.
An API, not a proxy string
You do not configure a proxy in your HTTP client. You POST a URL and a region to our API and get the target's response back. That is a meaningful difference: there is no proxy authentication dance, no per-language proxy configuration, and the same call works identically from a script, a serverless function or a browser backend.
It also means every request is metered exactly, and you can send an Idempotency-Key so that a retry after a timeout is not billed or executed twice.
Rotation, and what rotates
What changes between requests is the region you ask for, not an address pool inside it. Each region is served by one node on a stable address, so asking for us-east twice gets you the same exit twice; the failover that crosses regions is the only thing that moves you, and region_used in the response tells you when it did. We do not claim a pool of thousands of addresses, because we do not have one — see the locations page for the exact fleet.
The user agent does not rotate either, and that is deliberate. The fetch forwards your own User-Agent header to the target exactly as you sent it, so the identity presented is one you chose and can reproduce. The user-agent library is a catalog to read and pick from, not a rotation we perform on your behalf.
Get a key
Create an account and mint an API key in the dashboard. The full endpoint reference — request shapes, parameters and error codes — is published at https://api.roamingproxy.com/v2/docs.