Managed Proxies
Route browsers through residential IPs - from our managed proxies, or bring your own.
Managed residential proxies
Paid plans include managed residential proxies. Claim one, bind it to a profile, and launch. Usage is metered per month (see below).
Bring your own
Pass any protocol://user:pass@host:port URL to launch() - http, https or socks5. Your own proxies are never metered.
Authentication happens in the engine
Username/password proxies are answered by the browser engine itself: HTTP and HTTPS 407 challenges inside the network stack, and SOCKS5 by RFC 1929 username/password negotiation during the handshake. Two things follow. Nothing is loaded into chrome://extensions - the proxy-auth helper extension most antidetect browsers still ship is enumerable from any page, and it is exactly the kind of tell this product exists to remove. And the credentials only ever reach the network process, never a renderer, so no page script can read them.
Plan Quotas
Each plan allows a number of distinct proxies used per month (N). You may hold up to 2×N at once (claiming/holding is always free).
Acquisition
Claim (free)
Take an available managed proxy. It becomes stickily assigned to you. Claiming never consumes monthly quota - you can hold up to 2×N.
Release
Return a held managed proxy, freeing a hold slot.
Swap
Return one proxy and claim a new one in a single step.
Metering & Reset
Metering is by monthly active use: holding is free; launching is what counts.
Launching a profile with a managed proxy meters one distinct proxy for the current month.
Re-launching the same proxy in the same month is free (it only updates last-used/launch count).
Once you have used N distinct proxies this month, activating a new one returns 403 (monthly quota exceeded).
Monthly auto-reset: metering uses a UTC calendar month (YYYY-MM). At month start the count resets to zero automatically - proxies you keep using are admitted again, proxies you stop using simply free up.
Claiming, holding, and binding never meter. Bring-your-own proxies never meter.
API Reference
All endpoints require Authorization: Bearer <api-key>.
/api/v1/proxiesList your assigned proxies + monthly quota: limit, usedThisMonth, remaining, holdCount, holdCap.
/api/v1/proxiesManage your holdings via an action body:
{ action: 'claim' } - claim an available managed proxy (free){ action: 'release', proxyId } - release a held managed proxy{ action: 'swap', proxyId } - swap for a new one
/api/v1/proxies/:id/activateMeter + activate before launch. Idempotent within a month for the same (user, proxy). Returns 403 when the monthly limit is exceeded. The SDK calls this automatically when you pass proxyId.
Provider setup guides
Bringing your own account? Each guide has the three steps, the gateway and session parameters as that provider documents them, and a link back to their own reference.
Usage
From the Node SDK
import { listProxies, claimManagedProxy } from 'anti-detect-browser'
// See your managed proxies + quota
const { quota } = await listProxies({ key })
// { limit, usedThisMonth, remaining, holdCount, holdCap }
// Claim is free - does not touch monthly quota
const proxy = await claimManagedProxy({ key })
// Launching with proxyId meters one distinct proxy for the month
await ab.launch({ profile: 'acc-01', proxyId: proxy.id })// Bring your own proxy - never metered
await ab.launch({
proxy: 'socks5://user:pass@us-proxy.example.com:1080',
profile: 'us-account',
})The credentials in that URL are handled by the engine - 407 for HTTP/HTTPS, RFC 1929 for SOCKS5 - with no helper extension loaded. Both SDKs and the desktop app behave identically here.
From the Python SDK
# Bring your own - never metered
launch(profile="us-account", proxy="socks5://user:pass@us-proxy.example.com:1080")Claiming and quota live on the /api/v1/proxies endpoints above; the Python package launches with a proxy you already hold rather than wrapping those calls. See the Python SDK reference →
From the desktop app
On the Proxies page, claim a managed proxy (or add your own), then bind it to a profile in the create/edit dialog. Launching the profile meters the proxy for the month, exactly like the SDK. See the desktop walkthrough →