Every guide below shows the proxy form of one tool, names its fields exactly as the app labels them, and tells you which QuantumProxies host, port and username to paste. Residential, mobile, ISP, datacenter and IPv6 plans all use the same username:password login, so one guide covers every plan.
One profile, one proxy: these browsers store the proxy inside the profile, so every profile keeps its own IP. Use a sticky session in the username to keep the same IP for up to 24 hours.
Clash Verge, v2rayN and NekoBox route the whole device or selected apps through the proxy. They expect a plain HTTP or SOCKS5 server with username and password, which is exactly what the dashboard generates.
Copy the line from the dashboard (Proxies, your plan, the proxy generator) rather than typing it: it already carries the country, the session id and the session length in the username. The table shows what each field holds.
| Plan | Host | HTTP port | SOCKS5 port | Username shape |
|---|---|---|---|---|
| Residential Premium | residentialpremium.quantumproxies.io | 8080 | 1080 | USER-country-us-sid-k3f9a1b2-ttl-60m |
| Residential Basic | residentialboson.quantumproxies.io | 9000 | from the generator | USER-country-us |
| Mobile | mobile-us.quantumproxies.io (also -eu, -as, ww) | 8080 | 1080 | USER-country-us-type-mobile |
| Datacenter (per GB) | datacenterboson.quantumproxies.io | 9999 | 10000 | USER-type-datacenter-country-de |
| IPv6 | ipv6.quantumproxies.io | 1001 | from the generator | USER-country-us-package-ipv6 |
| ISP (dedicated IP) | the IP of your line | 8000 | on the plan page | the line's own login |
The password is the one the generator prints next to the username. Pick HTTP or SOCKS5 in the tool and use the port of that column; a port from the other column is the most common reason a check fails. USER and the session id are placeholders for your own values.
Each page follows the same four moves: open the profile or node editor, find the proxy block, paste host, port, username and password into the fields the tool names, then press the tool's own check button. The screenshot on every step is the real form of that version of the app, with the example values blurred, so you can match it against what you see on screen.
The values themselves do not change from tool to tool. What changes is the label on the field (Host, IP address, Proxy server, Address), whether the port sits in its own box or after a colon, and whether the app accepts a pasted host:port:user:pass line. Every guide spells that out.
QuantumProxies gateways answer on an HTTP port and a SOCKS5 port with the same host and the same login. The tool asks for one type; use the port of that type. Choosing HTTP with the SOCKS5 port, or HTTPS where the app means a TLS proxy, gives a timeout or an authentication error even when every other field is right.
When a tool offers both, HTTP is the safer default for websites: it is what every browser speaks natively. SOCKS5 is useful for apps that need UDP or non-HTTP traffic, and for clients such as Clash Verge or NekoBox that expect a SOCKS node.
Antidetect browsers only make sense if each profile keeps its own IP between launches. On the residential and mobile gateways that is set in the username: a sid value names the session and ttl sets how long the IP is held, from 3 up to 1440 minutes. Generate one line per profile with a different sid, paste each into its own profile, and the browser never has to rotate anything itself.
Dedicated ISP lines and static IPv6 sessions are fixed by nature: one line, one IP, for the whole plan. Those go into the profile as they are.
Either works. HTTP is the default for websites and uses the HTTP port of your plan; SOCKS5 uses the SOCKS5 port with the same host and login. Never choose HTTPS unless the tool documents it as a plain HTTP proxy: in most apps HTTPS means a TLS-wrapped proxy, which our gateways do not speak.
Many of the tools here (AdsPower, ClonBrowser, DICloak, Dolphin Anty, Lalicat, VMLogin, Undetectable, Incogniton, Linken Sphere) parse a host:port:user:pass line and fill the fields for you. The dashboard generator exports exactly that format; the guide of each tool says whether the paste box exists and where it is.
Generate a sticky line: the username carries a session id and a ttl of up to 1440 minutes, and the gateway returns the same IP for that session while it lasts. Give every profile its own session id. Dedicated ISP IPs and static IPv6 sessions do not change at all.
Mobile proxies on carrier IPs are the strongest choice for social platforms, followed by residential sticky sessions. ISP lines give one fixed IP per profile with unlimited sessions. All of them use the same login format, so the guide does not change with the plan.
The proxy check only proves the gateway answered. Match the IP country to the account's billing or usual country, give each profile its own session id, and avoid sharing one line across profiles. If a specific site keeps failing, Quantic AI in the dashboard can test the line and open a ticket with the exact error.
Any app with Host, Port, Username and Password fields takes the same values: pick HTTP or SOCKS5, paste the host and the port of that type, then the username and password from the generator. Quantic AI in the dashboard knows the field mapping and can walk you through it.
Skip the marketing. QuantumProxies.io publishes a machine-readable site map, Markdown for every page, a free MCP server, and APIs billed from the same balance as your proxies.
Connect in one command: npx -y quantumproxies-mcp