Proxy integrations
Guides for connecting the tools developers already use to one static ISP address. Each one was run against an authenticated proxy before it was published, and each says what did not work.
In short: Every address you buy has its own host, port, username and password, and runs HTTP, which carries HTTPS, or SOCKS5, switched on the order. An order authenticates one of two ways: by username and password, or by a whitelist of client IPs that you set through the API, and while the whitelist is set the password does not work. Each guide shows where its tool takes those values.
A proxy is set in a different place in every tool: a dictionary of schemes in requests, a browser option in Selenium, a launch or context argument in Playwright. The connection details behind them are the same four values, and the same rule decides whether a password or a whitelisted IP is needed.
Pick the tool you use
Questions about the integrations
Which guide should I start with?
The one for the tool your code already uses. Python requests covers scripts that fetch pages without a browser; Selenium and Playwright cover a real browser, with Playwright the simpler of the two when the proxy needs a password.
Should I connect over HTTP or SOCKS5?
HTTP, unless something you send is not web traffic or you want hostnames resolved at the proxy. HTTP is the protocol an order starts on and carries HTTPS as a tunnel. SOCKS5 needs the proxy switched on the order first, and browsers then need the IP whitelist instead of a password. SOCKS5
Where do I set the IP whitelist?
Through the API, with PUT /orders/ORDER_ID/whitelist, or with the set_proxy_whitelist tool of the MCP server. The dashboard has no control for it yet. The list takes IPv4 addresses, replaces the previous list on each call, and applies over HTTP and SOCKS5. While a whitelist is set, the proxy admits only the listed addresses and the username and password stop working for that order; sending an empty list turns the whitelist off and password login works again. MCP Server
Will there be guides for other tools?
Puppeteer, Scrapy and curl are the next candidates. We publish a guide only once its code has been run against a proxy, so there is no date for them yet.