← All proxy documentation

RapidProxy

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

Rotating residential with country, state and city all encoded in the username. Measured on a live account rather than read off a docs page.

1. Get the credentials

In your RapidProxy 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://<subaccount>-residential-BD-state-Chittagong-city-Chattogram-session-<id>-stime-10:<subaccount password>@us.rapidproxy.io:5001

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://<subaccount>-residential-BD-state-Chittagong-city-Chattogram-session-<id>-stime-10:<subaccount password>@us.rapidproxy.io:5001',
})
launch(
    profile="acc-01",
    proxy="http://<subaccount>-residential-BD-state-Chittagong-city-Chattogram-session-<id>-stime-10:<subaccount password>@us.rapidproxy.io:5001",
)

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

Parameters

Read off RapidProxy'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 us.rapidproxy.io
Ports 5001 for rotating residential, as printed in the panel's own test command.
Protocols HTTP and SOCKS5 are both offered in the panel; the readings below are over HTTP.
Options ride in the username
Country targeting -residential-<ISO2>, or -residential-GLOBAL for a random exit. -state-<name> and -city-<name> narrow it further, and they work: a Chittagong/Chattogram credential came out in Chattogram.
Sticky session -session-<id>-stime-<minutes>. Measured: the same session id returned the same exit across two separate browser launches; a different id landed on a different continent.
Session length stime is in minutes and the panel documents a ceiling of 180.
Source https://www.rapidproxy.io/

Worth knowing

  • The credential does not exist until you create a sub-account: until then the panel prints its test command with an empty username prefix, which looks like a working example and is not one.
  • Measured on 2026-09-12 with AntiBrow: launch to first page 2.0-3.7s, ipinfo.io in 3.3-3.8s. The browser timezone followed the exit every time - Asia/Dhaka in Bangladesh, Asia/Calcutta in India, Europe/Vienna in Austria.
  • No WebRTC leak: the srflx candidate carried a proxy-side address, never the local one. Worth knowing that it is not always the same address as the HTTP exit - on the Bangladesh run the page saw .35 while WebRTC surfaced .32 from the same /24.
  • A wrong password fails as net::ERR_TOO_MANY_RETRIES rather than an auth error - the same misleading symptom ProxyEmpire produces, so check the credential first.