Hypercall
A residential proxy network. You connect to a nearby edge with a normal HTTP or SOCKS5 proxy client, and your traffic exits through a real residential IP in the location you asked for.
Everything is controlled through the proxy username — geo, sticky sessions, TTL, and speed are all option tokens appended to it, so any client that supports username/password proxy auth works with no SDK and no special integration.
curl -x 'http://USER-country-us:[email protected]:4444' https://api.ipify.org
How it works
- One endpoint.
proxy.hypercall.devresolves to the edge nearest you. You never pick a region — the exit you want goes in the username. - Targeting is measured, not claimed. Exits are indexed by their real,
verified location and network, so
country,state,city, andasnreflect where the IP actually is. - Pay for what you transfer. Your balance is metered in bytes
(1 GB = 1,000,000,000 bytes). When it runs out, requests stop with
402.
Where to start
| Quickstart | Your first request, in one command |
| Connecting | Ports, protocols, proxy-string formats |
| Targeting options | The full username token grammar |
| Error codes | What each failure means and how to fix it |
| API reference | Manage accounts and sub-users over REST |