Fetch any page.
We handle the from-where.
A rotating HTTPS proxy on infrastructure we run ourselves — one key, three regions, and usage you can read back over the API.
Rotating proxy
Send a URL and a region — we fetch it from an egress address there. One POST, no session juggling.
User-agent library
The same curated catalog the proxy uses, readable over the same API with the same key.
Auditable usage
Your meter is an endpoint, not a PDF. Query what you've used — and what it costs — any time.
Up and fetching in three steps
Create your account
30-day trial, no card required.
Mint a key
Scoped, revocable, shown once.
Make the call
Copy a snippet that runs as-is.
curl -X POST \
"https://api.roamingproxy.com/v2/proxy/fetch?region=europe" \
-H "x-api-key: rp_your_key_here" \
-d '{"url": "https://example.com"}'
→ 200 · "region_used": "europe"Three regions, and honest edges
Egress runs from us-east, us-west and europe — datacenter nodes in our own AWS account, with the live list served by the API rather than promised by this page. There is no residential pool, no SOCKS5, no JavaScript rendering and no search-engine results, and the proxy-types page says so before you integrate, not after. What you can check, we publish: every refusal carries a stable error code, retries with an Idempotency-Key bill once, and the FAQ answers the questions that decide whether we fit.
$25/month with 50,000 requests in. Then $0.50 per 1,000.
Metered monthly, billed by invoice. Volume quotes: billing@roamingproxy.com · full details on pricing.
