Документація
Як підключитися, як працює таргетинг і що змінювати, коли приходить помилка.
Підключення
Рядки підключення, сесії, таргетинг і протоколи
Connection string reference
Everything our proxies accept, in one place. Residential targeting rides inside the login; static addresses take no suffixes at all.
Rotating and sticky sessions
Rotation is the default. A session identifier turns it off for as long as you ask, up to one hour.
Country and city targeting
Targeting is a suffix on the login. Country is reliable, city depends on which devices are online at that moment.
Protocols and ports
Every product speaks HTTP and SOCKS5. Where they differ is which port answers and whether DNS resolves on your side or ours.
Authentication and IP whitelisting
Everything authenticates by login and password. Residential lists can additionally trust your server addresses without credentials.
Розбір помилок
Що означає кожна помилка і що з нею робити
407 Proxy Authentication Required
A 407 comes from us, not from the site you were trying to reach. The destination never saw the request.
502 and 400: no exit available
Both mean the gateway could not give you what you asked for. Neither is a fault in your credentials.
Slow responses and timeouts
Most timeout reports turn out to be a client configured for datacenter latency talking to a residential route.
The documentation answers three different questions: how to connect, how to control the exit, and what a particular error means. If this is your first visit, read in order rather than by the table of contents.
The order to read in
Four pages cover ninety percent of the questions, and this is the order to open them in.
- The connection string. What the host, the port and the login suffixes are, and how the gateway differs from a static address.
- Protocols and ports. Where HTTP sits, where SOCKS5 sits, and why static addresses have their own ports.
- Geo targeting. How country and city are set, and why asking for a city hinders more often than it helps.
- Rotation and sticky sessions. When the address changes on every request and when it is held for up to fifty minutes.
What each response code is telling you
Separating these matters more than it seems: three of the five are fixed differently and two are not about us at all.
- A 403 on the very first request is address class. The target filters hosting ranges, and the fix is moving to residential rather than changing country.
- A 407 is authentication. The login and password did not reach the gateway in the form the tool expects.
- A 429 after a run of successful requests is pace. What you need is more addresses or a sparser pass; address class is irrelevant.
- A 502 or a 400 is an upstream response or a malformed request: look at the connection string and at what the client actually sent.
- A timeout with no status code is the network. It does not mean you were noticed, and reading it as blocking inflates your own failure statistics.
What the documentation deliberately leaves out
We sell addresses rather than a way past detection, and the documentation is written accordingly.
There are no instructions here for getting past anti-bot systems, for forging fingerprints, or for passing checks a target puts up deliberately. We do describe that such checks exist and what the refusal looks like, so that you do not go looking for the problem in the proxy.
The legal part is stated plainly too: the country pages say which personal data legislation applies and that it does not depend on the address you exit from.
Questions about the documentation
Which page should I start with?
The connection string. It explains the host, the port and the suffixes, and without it the other pages read as a list of special cases.
How does a 403 differ from a 429?
The first is about address class and is fixed by moving to residential. The second is about pace and is fixed by more addresses or a sparser pass.
Is a timeout a block?
No. It is a network event with no status code, and separating it from refusals in your logs keeps your blocking statistics honest.
Is there an API and machine-readable data?
Yes. The public REST API is documented separately, and prices and limits live at /pricing.txt and /llms-full.txt so they can be read without parsing the site.
Шукаєте API?
Купівля, продовження і список проксі йдуть через REST, а MCP-сервер дає ті самі операції ШІ-агентам.