About IPIDEA

What we run

Six product lines share one pool and one balance: residential, static residential/ISP, SOCKS5 and HTTP(S), datacenter, rotating ISP and mobile. Customers move budget between them as projects change rather than holding several subscriptions.

How we price

Traffic plans start at $5, per-IP plans at $0.05 and static ISP at $1.50 per address. There is no monthly minimum, no geo surcharge and no expiry on balances — an unused IP is still an IP next quarter.

Who uses it

Data and automation teams, marketplace sellers, research firms and agencies running collection, brand protection, ad verification workloads. The common requirement is continuity: sessions that survive, geographies that are accurate, and pricing that does not change shape mid-project.

Support and payments

Checkout accepts USDT (TRC20/BEP20/ERC20), BTC, LTC, TRX, ETH and XMR. Registration is email-only. Support runs through live chat and the contact page.

How the network is built

The residential layer is sourced through partner applications where users opt in knowingly, and the pool is refreshed continuously so addresses that go stale drop out rather than lingering in rotation. Static ISP capacity sits on carrier infrastructure and is provisioned per customer, which is why those addresses hold for the life of a plan instead of drifting.

Everything above that is configuration. Country, city, ISP and session mode are encoded in the credential itself, so a single account can hold dozens of distinct setups at once without provisioning anything new or waiting on an approval step.

What we do not do

There is no reselling of another network's pool under our name, no bandwidth throttling dressed up as a plan tier, and no geo surcharge that quietly triples the cost of the one market a project actually needs. Balances do not expire, so a paused project does not forfeit capacity that was already paid for.

We also do not pretend residential is always the answer. Where a target is insensitive and the job is throughput-bound, datacenter exits are cheaper and faster, and support will say so before an order rather than after it.

Acceptable use

IPIDEA exists for market research, quality assurance, brand protection, ad verification and automation of public workflows. The acceptable-use policy draws the boundary explicitly, and accounts that cross it are closed. That is not a formality — abuse degrades the pool everyone else depends on, which makes enforcement a product decision rather than a legal one.