System nominal·Exit pool: PL only·Carriers: 4 / 4·Active scans: 2,418--:--:-- WARSAW·--:--:-- UTC
INTEGRATION · KAMELEO

Kameleo proxy integration with Polish mobile exits

Kameleo sets the proxy per profile in the desktop app and through its local API. Bind a sticky StealthProxy lane — up to a 30-day window — and each Kameleo profile keeps the same Polish 4G/5G mobile or residential exit, ASN and carrier for the life of the identity.

Where
Profile → Proxy
app + local API
Sticky
Up to 30d
per profile
Exit
PL mobile
ASN-stable
STEP BY STEP

Setting the proxy in Kameleo

Kameleo can take the proxy in the desktop UI or over its local automation API — both attach the lane to the profile so it launches through the same Polish exit each time.

1 · Create a profile, open Proxy

In the Kameleo app, create a profile from a base fingerprint, then open the Proxy step. Choose SOCKS5 (HTTP works too) with custom/manual entry rather than no proxy or a built-in option.

2 · Paste host, port and credentials

Enter proxy.stealthproxy.io, the port from your dashboard, and the username/password. The username encodes the carrier and a long sticky window, so the profile binds to one Polish exit and ASN (e.g. AS12912) for up to 30 days.

3 · Or attach it via the local API

For automation, pass the proxy object to Kameleo's local API when you create or start the profile — type: "socks5", host, port, and credentials. Then align the profile timezone to Europe/Warsaw and language to pl-PL so the spoofed fingerprint matches the IP geo.

WHAT YOU GET

Built for Kameleo profiles

KM/01

App + API setup

Attach a sticky lane in the Kameleo desktop UI or programmatically through its local automation API.

KM/02

30-day sticky

Use a long sticky window so each profile holds the same Polish mobile IP, ASN and carrier for the life of the identity.

KM/03

Carrier-pinned exits

Lock a profile to Orange, T-Mobile, Play or Plus for a stable, real Polish 4G/5G origin across every launch.

KM/04

Geo ↔ timezone match

Europe/Warsaw timezone and pl-PL locale on a Polish IP keep the Kameleo fingerprint coherent.

SPEC SHEET

Kameleo proxy fields at a glance

config · kameleo
WhereProfile → Proxy (app) or local API
TypeSOCKS5 (or HTTP)
Hostproxy.stealthproxy.io
Port / authFrom dashboard · username:password
StickyUp to 30 days per profile
ASNStable Polish mobile (e.g. AS12912)
AlignmentEurope/Warsaw ↔ Polish IP ↔ pl-PL
FAQ

Kameleo proxy questions

How do I set a proxy in Kameleo?+
Open the profile Proxy step, choose SOCKS5 or HTTP with custom entry, and paste host, port and credentials from your dashboard. The profile then launches through that Polish exit.
Can I set the proxy via the Kameleo API?+
Yes — pass the proxy object (type socks5, host proxy.stealthproxy.io, port, credentials) to the local API when you create or start a profile.
Does Kameleo keep the same IP per profile?+
Yes with a sticky lane. Use a long sticky window (up to 30 days) so each profile keeps the same Polish mobile IP, ASN and carrier.
NEXT STEP

Set up your first Kameleo profile

From signup to first profile

See the pricing for per-IP rates, then create an account and bind your lane in the Kameleo app or API. For the alignment theory behind it, read browser fingerprint proxy.

FREE TRIAL

Pair one browser profile with a clean IP, free

Take a real mobile IP for an hour, no card. Bind it to a single antidetect profile, confirm the fingerprint holds, then scale your stack.