ProxyEmpire

Point a browser profile at ProxyEmpire residential proxies. Three steps, no plugin, no proxy-auth extension.

Rotating residential behind one gateway, with the session id in the username. Unlike the other entries on this page, these values were not read off a docs page - they were measured on a live account.

1. Get the credentials

In your ProxyEmpire dashboard, open the residential product and copy the gateway host, the port, and the username and password. Everything below assumes those four values.

2. Build the proxy URL

One string, credentials included. Targeting and session options go in whichever half this provider puts them in - the table below says which.

http://r_<account>-sid-<session>:<password>@v2.proxyempire.io:5000

3. Launch

Timezone, locale and WebRTC are derived from the exit address, so a US exit does not arrive with your own timezone attached.

await ab.launch({
  profile: 'acc-01',
  proxy: 'http://r_<account>-sid-<session>:<password>@v2.proxyempire.io:5000',
})

launch(
    profile="acc-01",
    proxy="http://r_<account>-sid-<session>:<password>@v2.proxyempire.io:5000",
)

Prefer not to run an account at all? Managed residential proxies are included on paid plans.

Parameters

Read off ProxyEmpire's own documentation on 2026-09-12. Ports and endpoints differ by plan and by zone, so where this table and your dashboard disagree, the dashboard is right.

Gateway	v2.proxyempire.io
Ports	5000 for rotating residential, as printed in the panel's own Connection Builder.
Protocols	HTTP. The panel prints a ready-made curl line using an http:// proxy URL.
Options ride in	the username
Country targeting	The panel's Connection Builder rewrites the username when you pick a country, so copy the string it produces rather than assembling one.
Sticky session	-sid-<id> in the username. Measured: the same sid returned the same exit IP across two separate browser launches, and a different sid returned a different IP and a different ISP.
Session length	The panel offers Same IP, Every request, or a custom TTL in minutes.
Source	https://proxyempire.io/residential-proxies/

Worth knowing

Measured on 2026-09-12 with AntiBrow: launch to first page in about 2s, ipinfo.io in 2.4-3.7s, and no WebRTC leak - the srflx candidate carried the proxy address while the host candidate stayed an mDNS .local name.
A wrong password does not surface as an auth error inside the browser: the page fails with net::ERR_TOO_MANY_RETRIES. Check the credential in the panel before debugging anything else.