How to add a proxy in Incogniton

Incogniton takes a proxy either as an address with the credentials in their own boxes, or as one combined string it splits for you, and it will import a list from a CSV.

This covers all of those, how to read the status icons it shows afterwards, and how to launch a profile from the local API.

What is Incogniton?

Incogniton is an anti-detect browser built around browser profiles with separate fingerprints and proxies, with its own proxy shop attached.

Incogniton proxy features

Five documented input shapes

More than most, and they overlap. The two that matter for a single proxy:

ip:port                          into the address field, credentials separate
ip:port:username:password        into the SAME field, split automatically

The second is documented plainly: "You can also paste the full credentials string directly into the ip:port field using the format ip:port:username:password and Incogniton will populate the remaining fields automatically."

Their reminder for the first form is worth keeping: "Make sure the port is included in the proxy address field, in the format ip:port."

Bulk add, with a file route

"Paste your proxy list into the text field, one proxy per line, using the format ip:port:username:password. You can load your proxy list from a CSV file by selecting Load from file."

A CSV path is rarer than it should be in this category. Multilogin caps a pasted list at twenty-five with no import at all.

Allowlisting, but only on their own proxies

Documented in exactly one place, and scoped: "You can also whitelist up to 5 IP addresses for authentication. This is optional and can be edited at any time after purchase."

That sentence is on the Proxy Shop purchase page. It is about proxies bought from Incogniton, not about a third-party proxy you attach. For those, the username and password fields are the only documented route.

Adding a proxy

1. Enter the address in the field labelled with the ip:port format.
2. Fill the username and password boxes, or skip them by pasting the combined string into the address field instead.
3. Confirm the connection type matches what your provider issued.

The red icon that is not a failure

Here is the sentence, and it is the most useful one on the page:

"If you're seeing a red lightning bolt icon with the green check rather than a red cross, that's a slow proxy speed, not a connection failure. See Proxy speed instead."

Three states, then:

The middle row is the trap. It is red, it appears where an error appears, and it is not an error. Re-entering your password because of it is time spent on a problem that does not exist, and the real answer is a slower exit node.

Their framing for the genuine failure: "If a profile gives a connection error, or shows a red cancel icon and fails to launch, the cause is almost always one of a few common configuration issues. Follow these solutions in order before assuming the proxy itself is broken."

The first check they list is the protocol, not the credentials, which is the right order and the opposite of where most people start.

Automating it

The local API is on port 35000, and the simplest call is a plain GET.

curl http://localhost:35000/profile/launch/{profile_id}

The Python SDK wraps the same endpoint and hands back a Selenium driver:

from incogniton import Incogniton

client = Incogniton(base_url="http://localhost:35000")

# The API's proxy fields, which their docs mark as used "if applicable".
client.profile.update(PROFILE_ID, {
    "proxy_host": "gate.example.com",
    "proxy_port": "7000",
    "proxy_username": "user-session-abc123",
    "proxy_password": "secret",
})

driver = client.selenium.launch(PROFILE_ID)
driver.get("https://example.com")
driver.quit()
client.profile.stop(PROFILE_ID)

Node takes the same shape:

import { Incogniton } from "incogniton";

const client = new Incogniton({ baseUrl: "http://localhost:35000" });
const browser = await client.puppeteer.launch(profileId);
const page = await browser.newPage();
await page.goto("https://example.com");
await client.profile.stop(profileId);

There are no API tokens: authentication is the running desktop app, and the CLI's --port flag exists because the port is configurable in the app's Debug settings. Their instruction is to pass it every time if you have changed it.

It is gated behind a paid plan twice over. Automation is excluded from the free package, and their comparison table shows REST API access and Selenium or Puppeteer support both unavailable on the entry tier. Their CLI page restates it: "The CLI requires a paid Incogniton subscription that includes automation."

So the code above follows Incogniton's documented endpoints rather than a run of ours. Compare MoreLogin, whose free plan includes the local API outright.

The free plan expires into a smaller one

This is not a permanent free tier and the wording repays attention:

"Get started with our free starter package, which includes 10 browser profiles for the first 2 months. After that, the package will update to 3 profiles."

Ten, then three. No card required, and no automation at any point.

If you are trialling this against a proxy purchase, the useful window is two months and the thing you cannot trial at all is the API.

Whichever tool you settle on, the proxy behind it is the recurring cost, and per-gigabyte prices vary far more between providers than these applications vary between each other. What each charges, with the date it was read, is on the provider table.

Limitations

Automation excluded from free and from the entry paid tier.

The allowlist is five addresses, and only on Proxy Shop proxies.

Free shop proxies cover nine countries, listed as us, hk, br, nl, au, uk, de, in and ua.

What the documentation does not say

The gap here is unusually specific, and it is the exact thing people search for.

"proxy status no connection" appears on no Incogniton page. We searched both of their concatenated full-text documentation exports, 305 KB and 154 KB, plus the legacy knowledge centre, case-insensitively, for that phrase and for "no connection", "connection failed", "proxy status" and "ERR_". The only hits were a page title, a subtitle, and three changelog lines about error messages in general.

Incogniton never publishes the status text its own interface shows. Every description of a failure is an icon: "a red cancel icon", "a red cross", "a red lightning bolt icon with the green check". There is no status-string table anywhere, which is why searching the exact words on your screen returns other people's blogs rather than the vendor.

Also unestablished: whether an IP-allowlisted third-party proxy can be used at all, since allowlisting is documented only for their own shop.

Whichever entry route you use, the session token sits in the username at some providers and the password at others. What each states is on its provider page, dated.

Conclusion

Learn the two red icons before anything else, because one of them will otherwise cost you an evening. Prefer the separate credential boxes to the combined paste. And treat the free package as a two-month trial with no API rather than a free tier, because that is what the pricing page says it is.