Setting Up IPIDEA: Credentials, Targeting and Your First Verified IP

IPIDEA has no desktop client, and it does not need one. Everything the network can do — country, city and ISP targeting, sticky or rotating sessions, protocol choice — is expressed in the credential string you paste into your tool. Learn to read that string and the rest of the setup takes about five minutes.

Anatomy of an IPIDEA credential

An IPIDEA endpoint is four things: a gateway host, a port, a username that carries configuration, and a password. The host and port stay constant. The username is where the work happens — every targeting decision travels inside it, which is why one account can drive dozens of different configurations without provisioning anything new.

That design has a practical consequence worth internalising early: you never wait for an account change to test a different country. You edit a string and reconnect.

Encoding country, city and ISP

Targeting narrows in three steps, and each one costs the same — there is no geo surcharge anywhere in the network.

• Country — the default granularity, right for broad crawls and coverage tests.
• City — necessary wherever pricing, stock or ad delivery changes by metro. A national average tells you nothing useful in those cases.
• ISP — for targets that treat carriers differently, which is more common on mobile-first and telco-adjacent properties than most teams expect.

All three are available across 220+ countries and regions. Combine them freely; a request can be pinned to one carrier in one city if the job calls for it.

Sticky versus rotating, and when each is wrong

Rotation gives you a new IP per request. That is correct for stateless collection and actively harmful for anything with a login — a session that changes address mid-flow reads as a hijack attempt to most platforms.

Sticky sessions hold one address for up to thirty minutes, which covers a cart, a form sequence or a logged-in check. Beyond that window, stop reaching for sticky and move to static ISP: an identity that must persist for months is a product decision, not a session parameter.

Wiring it into browsers, scripts and fleets

SOCKS5, HTTP and HTTPS accept the same credentials, so tooling choice never forces a purchase.

• curl — curl --socks5-hostname user:pass@host:port https://example.com. Use --socks5-hostname, not --socks5, so DNS resolves at the exit rather than locally.
• Python — install requests[socks] and pass socks5h:// in the proxies dict. The trailing h matters for the same DNS reason.
• Playwright / Puppeteer — --proxy-server=socks5://host:port, then authenticate on page load.
• Antidetect browsers — host, port, login and password go into the profile's proxy tab; nothing else is required.

Verifying the exit before you trust it

Never assume a configuration worked because it connected. Three checks, every time you change something:

1. Geography — does the reported country, city and ISP match what you asked for?
2. DNS — is resolution happening at the exit? A local resolver leaks your real location regardless of how clean the IP is.
3. Session behaviour — request twice. Sticky should return the same address; rotating should not.

A configuration that passes all three is safe to build on. One that passes only the first will fail later, in production, for reasons that look mysterious.

Scaling from one endpoint to many

Concurrency is unlimited, so scaling is an orchestration problem rather than a billing one. The pattern that holds up: generate endpoints through the API per task, let the worker retire its endpoint when the task finishes, and keep sub-accounts aligned to teams or projects so usage attribution stays honest.

Treating endpoints as disposable also contains failure. A job that gets itself blocked burns one short-lived credential instead of contaminating something long-lived.

FAQ

Is there an IPIDEA client to install?

No. The network is credential-based, and any download claiming otherwise is a reupload you should not run.

Can one account use several countries at once?

Yes. Targeting lives in the credential, so parallel jobs can each hold a different market.

Why is my IP not the country I selected?

Almost always DNS resolving locally. Switch to socks5h:// or --socks5-hostname.

What does it cost to start?

Plans begin at $5; code IPD30 takes 30% off a first order.