Same network, same $4.00/GB, same username DSL as the Pool Gateway. What Private Pool adds is named, country-scoped credentials - one per project or per customer, each with its own usage series - and Reserved IPs, specific exit devices held for you alone.
This page is a pointer, not a second manual. The product, pricing and the username DSL are documented once on the Pool Gateway page and in /pool/skill.md. Only what is genuinely different lives here.
What is different
Scoped credential. A pool is pinned to a country list you choose, with its own label, its own secret, and its own per-day usage series - so you can bill or debug one project without untangling it from the rest of your traffic.
Reserved IPs (leases). A lease holds one specific exit device exclusively - nobody else is routed through it while you hold it. Pin with -pin-lease-<leaseId>. Rotating a lease swaps the device but keeps the id, so your connection string never changes.
Two funding models. A pool draws either on your account's global GB, or on a specific purchase claimed by that pool. Which one you have changes what runs out first.
23 REST endpoints to create, scope, meter, reveal, rotate and lease - all with an ordinary account API key.
Start here
/private-pool/skill.md - the canonical, machine-readable reference: auth, every endpoint with real response shapes, the funding-model table, leases, and the error codes. Written for agents; equally readable by humans.
Exit IPs are never returned by any endpoint - you get country, carrier, ASN and type. Published exit IPs get burned by anti-bot IP-reputation systems, which would degrade the network for every customer on it.
See also
Pool Gateway - the product, pricing, and the full username DSL