Integrate in minutes, not days.
Everything you need to route traffic through BifrostNetwork: authentication, the endpoint syntax, protocol support, and working code in three languages.
Quick Start
- Create an account and order any plan from your dashboard — credentials are issued instantly, no waitlist.
- Copy the connection string shown on your order (username, password, and gateway host).
- Send a test request. If it returns a residential IP that isn't yours, you're connected.
$ curl -x socks5h://resi.eco_b28ed8682f-country-us:<pass>@gate.bifrostnetwork.cc:9521 https://httpbin.org/ip
{ "origin": "203.0.113.42 (US Residential Node)" } Authentication
Every request authenticates via standard proxy Basic Auth, embedded directly in the connection URL — no separate API key or OAuth flow. The username itself encodes your plan and routing options.
protocol://username:<pass>@gate.bifrostnetwork.cc:9521 Rotate your password anytime from the Telegram bot's account menu — active sessions using the old password are cut over on their next connection.
Endpoint & Session Syntax
The username is a dash-delimited string: your plan code, account ID, and any number of routing modifiers.
<plan>.base_<account_id>-country-us-session-3439b03c-ttl-300 | Modifier | Example | Effect |
|---|---|---|
| -country-xx | -country-de | Routes through an exit node in that ISO country code. |
| -session-id | -session-3439b03c | Pins the same exit IP across requests sharing this ID (sticky session). |
| -ttl-seconds | -ttl-300 | Sticky session lifetime. Defaults to 600s if omitted. |
| (omit -session) | — | Every request gets a freshly rotated exit IP. |
Protocols
The same gateway and credentials work across all three — pick a protocol per-request, no separate accounts needed.
SOCKS5
Recommended default. Supports both TCP and UDP ASSOCIATE, so it also carries QUIC traffic.
HTTP / HTTPS
Standard CONNECT tunneling — drop the same credentials into any HTTP client's proxy settings.
UDP / QUIC
Native support for HTTP/3 and latency-sensitive workloads that legacy TCP-only proxies can't carry.
Geo & ASN Targeting
Narrow the exit pool by ISO country code or carrier ASN (residential plans support ASN targeting). Unsupported combinations automatically fall back to the nearest matching tier.
resi.eco_b28ed8682f-country-us-asn-7018 Code Examples
curl
$ curl -x socks5h://resi.eco_b28ed8682f-country-us-session-288ed66a:<pass>@gate.bifrostnetwork.cc:9521 https://httpbin.org/ip Python (requests)
# pip install "requests[socks]"
import requests
proxy = "socks5h://resi.eco_b28ed8682f-country-us-session-288ed66a:@gate.bifrostnetwork.cc:9521"
r = requests.get("https://httpbin.org/ip", proxies={"http": proxy, "https": proxy})
print(r.json()) Node.js
// npm install socks-proxy-agent
import { SocksProxyAgent } from "socks-proxy-agent";
const agent = new SocksProxyAgent(
"socks5h://resi.eco_b28ed8682f-country-us-session-288ed66a:@gate.bifrostnetwork.cc:9521"
);
const res = await fetch("https://httpbin.org/ip", { agent });
console.log(await res.json()); Troubleshooting
| Symptom | Likely cause & fix |
|---|---|
| 407 Proxy Auth Required | Username or password doesn't match what the bot issued — re-copy the connection string, it's case-sensitive. |
| Connection timeout | Client is set to plain SOCKS5 instead of socks5h — DNS must resolve through the proxy, not locally. |
| Same IP every request | A -session- ID is present (or being reused) — omit it or generate a new one to force rotation. |
| Empty country pool | Specified region pool is temporarily empty — system automatically falls back to nearest available nodes. |
Using the Chrome Extension
Bifrost Proxy Manager is a Manifest V3 Chrome extension that connects to the official Bifrost proxy — or any HTTP/HTTPS/SOCKS5 proxy — without leaving your browser. This section covers install, setup, and troubleshooting.
Install
- Install Bifrost Proxy Manager from the Chrome Web Store.
- Pin the extension to your toolbar for one-click access.
- Click the icon to open the popup — this is where you'll switch modes, manage profiles, and check your connection.
Connect With Your Account Token
To use the official Bifrost proxy network through the extension, you need an account token instead of a plan connection string.
- Log in to your dashboard and copy your account token from Settings → Account API Token.
- Open the extension popup, go to Settings, and paste the token into Bifrost Account API Token.
- Back in the main popup, select Bifrost Official Proxy as the mode, choose a plan and target region, and click Enable Proxy.
Once your token is set, the popup automatically fetches your purchased plans, available regions, and gateway credentials — no need to construct a connection string by hand.
Custom Proxy Profiles
If you're not using the official Bifrost network — or want to switch between several proxies you already run — use Custom Proxy Profile mode.
| Field | Description |
|---|---|
| Protocol | HTTP, HTTPS, or SOCKS5 |
| Host / Port | Your proxy's gateway address |
| Username / Password | Optional — leave blank for unauthenticated proxies |
| Profile name | A label so you can find it again (e.g. "Work VPN", "Home server") |
Save as many profiles as you need. Switching between them — or back to the official Bifrost proxy — is one click in the popup; none of your saved credentials need to be re-entered.
Verify Your Connection
Every time you enable a proxy, the popup runs an exit IP and geolocation check automatically. The result is shown directly under the connection toggle, so you can confirm the switch actually took effect before you start browsing.
Bypass List
Local and internal addresses can be kept on a direct connection regardless of which proxy mode is active. In Settings → Bypass List, add one rule per line:
<local>
127.0.0.1
localhost
*.local
192.168.0.0/16 Auto Sign-In
For proxies that require authentication, the extension supplies your saved username and password via Chrome's chrome.webRequest authentication API. This means:
- No login popup ever appears, even on proxies that would normally prompt Chrome's native auth dialog.
- Credentials stay in Chrome's local extension storage — they're never synced to a third-party server, only sent to the proxy itself (or the Bifrost API, for official-proxy mode).
Troubleshooting
| Symptom | Likely cause & fix |
|---|---|
| "No API token configured" | No account token has been saved yet — add one under Settings → Account API Token, or switch to Custom Proxy Profile mode if you don't have a Bifrost account. |
| Exit IP unchanged | Chrome may still be using a cached connection — reload the page you're testing on, or toggle the proxy off and on. |
| Repeated auth prompts | Username/password weren't saved correctly in the profile — re-open the profile and re-enter credentials. |
| Can't reach local network | Add the device's address or subnet to the Bypass List (see above). |
| No available plans | Your account token may be expired or invalid — copy a fresh token from the dashboard. |
Using BifrostBrowser
BifrostBrowser is a fingerprint (anti-detect) browser included free with every Bifrost proxy account. Each profile is a fully isolated environment — its own cookies, cache, and a coherent hardware/software fingerprint — with proxies and fingerprint templates managed from the same app.
Install
Download the build for your OS from the BifrostBrowser download section — the page auto-detects your system and recommends the right installer.
| OS | File |
|---|---|
| macOS (Apple silicon) | BifrostBrowser.dmg |
| Windows 10/11 (64-bit) | BifrostBrowser.exe |
| Linux (Debian 10+ / Ubuntu 20.04+) | BifrostBrowser.deb |
If macOS reports "BifrostBrowser.app is damaged and can't be opened," this is Gatekeeper quarantining an unsigned app, not a corrupted download. Clear it from Terminal:
sudo xattr -rd com.apple.quarantine /Applications/BifrostBrowser.app On first launch, open Settings → BifrostNetwork Account Token, paste the token from your dashboard user menu, and click Open Browser to Login to link the app to your account.
Workspace Overview
- Workspace — Browsers (your profile list — name, status, proxy, notes, last used) and Proxies (your saved proxy pool).
- Library — Fingerprints, a browsable set of real-device fingerprint templates.
- System — Settings.
The Browsers dashboard shows live counts across the top: total profiles, how many are currently running, saved proxies, and fingerprints available in your library.
Create a Profile
From Browsers, click + New profile (or From template to start from a curated fingerprint instead of building one field-by-field). The editor is grouped into five sections:
Identity
- Profile name — a label to find it later, e.g.
shop-pl-1 - Operating system — macOS / Windows / Linux
- GPU / device — pulled from the Fingerprint Library (e.g.
win-gt730) - User-Agent — auto-filled to match the selected device
- CPU cores / Memory (GB) — reported hardware specs
- Proxy — attach a saved proxy, or leave as direct connection
Locale
- Timezone — Auto (from proxy geo) keeps it consistent with the attached proxy's exit location, or set manually
- Language — same auto-from-proxy option
Noise
Per-signal toggle between Real (pass through the templated fingerprint's real value) or Auto noise for: Canvas, WebGL, Audio, Client rects, Sensors, Fonts. There's also a Ports to block list (defaults include common remote-access ports like 3389, 5900/5901, 5938) — add or remove ports as needed.
Privacy
- WebRTC — Auto (or set explicitly)
- Do Not Track — Off / On
- Geolocation — Auto (from proxy) or manual coordinates
Media Devices
- Mic in / Speakers / Webcam — number of virtual devices reported
- Notes — free-form field for your own reference
Click Create profile when done.
Fingerprint Library
Library → Fingerprints holds the device snapshots that populate the GPU/device selector in the profile editor. Templates are organized by OS (macOS, Windows, Linux) and named by device (e.g. mac-m1-air13, mac-m2-pro-mbp14), each tagged with a Chrome version and renderer string pulled from a real machine. Click Use → on any card to start a new profile from it, or expand the library with Import from file or + Paste JSON using a fingerprint exported from another working BifrostBrowser profile.
Add a Proxy
Go to Proxies and use the BifrostNetwork Proxy Quick Generator to pull directly from your purchased plans instead of hand-typing connection strings:
| Field | What it does |
|---|---|
| Select plan | Your active Bifrost plans, fetched automatically once your account token is linked |
| Target country/region | Pick a country, or leave as Any Country for a random exit |
| Session mode | e.g. a fresh IP per request, or a sticky session |
| ASN (optional) | Pin to a specific carrier/network, e.g. 7018 or AS7018 |
| Proxy protocol | SOCKS5 (or HTTP/HTTPS) |
| Quantity | How many proxies to generate in this batch |
Click Generate and batch import to create and add them straight to your Proxies list, ready to attach to any profile. This uses the same account and plans as the rest of the Bifrost gateway — see the endpoint syntax above if you'd rather build a connection string manually.
Automation API
BifrostBrowser exposes a local HTTP API for scripting — create, launch, and close profiles, and fetch a CDP WebSocket URL to drive them with Playwright, Puppeteer, or any CDP-compatible client.
- Binds to
127.0.0.1only — not reachable from other machines. - Auth: JWT Bearer token — send
Authorization: Bearer <token>. - Default port:
40325, shown as the Base URL and pinned at the bottom of the sidebar for quick copying.
GET/POST http://127.0.0.1:40325/...
Authorization: Bearer <token> Settings Reference
| Setting | Purpose |
|---|---|
| Account Token | Links the app to your Bifrost account so plans and proxies can be fetched automatically |
| Default startup page | URL opened when a profile launches — defaults to https://ip.sb for a quick IP check |
| Proxy geo checker | Which free IP-geo service the Test button uses to verify a proxy's location |
| Screen resolution | From fingerprint (recommended) reports the profile's templated screen size; Real exposes your actual monitor size |
| Automation API | Enable/disable the local scripting API, set its port, and manage the Bearer token |
Troubleshooting
| Symptom | Likely cause & fix |
|---|---|
| "App is damaged" on macOS | Gatekeeper quarantine flag on an unsigned app — run the xattr command above. |
| No plans in Quick Generator | Account token isn't linked yet — add it under Settings → Account Token. |
| Profile launches on your real IP | No proxy attached — set one in the profile's Identity section, or generate one under Proxies. |
| Automation script gets 401 | Bearer token is wrong, was regenerated, or the API server is disabled — check Settings → Automation API. |
| Automation script can't connect | Confirm Enable API server is on and you restarted the app after changing the port. |