Use cases
What runs on Basil.
Pokémon Center queues, ticket on-sales and sneaker restocks, and the cook groups and bot developers behind them. Same pool, same credentials. The string changes with the job.
Pokémon Center
One IP through the whole queue. Held for up to 24 hours.
A queue remembers where you connected from. Point the task at port 4243 with a session token and every request leaves from the same residential IP until its lifetime runs out, anywhere from 1 to 1,440 minutes. The country token puts that IP in the store's own market.
The Pokémon Center page# Sticky US session, same IP for two hours (port 4243) http://USER-country-us-session-k4mz61pq-lifetime-120:[email protected]:4243
Ticket drops
Exit where the on-sale is. Country first, then city.
Regional on-sales care where a buyer connects from. One token picks the exit country, a second narrows it to a city, and the session token holds that IP from queue to checkout. Running a team? Split one balance across up to five sub-accounts, each with its own credentials.
The ticket drops page# New York exit, held from queue to checkout http://USER-country-us-city-newyork-session-x9d02mvq-lifetime-60:[email protected]:4243
Sneakers & retail
Rotate to watch. Stick to check out.
A monitor wants a fresh IP on every request, and port 4242 hands you one. Checkout wants one IP from cart to confirmation, and port 4243 holds it. Where a site is hard on residential traffic, run an ISP proxy instead: a dedicated IP on our own ASN that stays yours after renewal.
The sneakers & retail page# Monitor: a new IP per request (port 4242) http://USER-country-us:[email protected]:4242 # Checkout: one IP for 30 minutes (port 4243) http://USER-country-us-session-m2p8zq4r-lifetime-30:[email protected]:4243
Cook groups
Proxies for the whole group. Priced for your members.
A group discount code can require membership of your Discord server. It's checked live at checkout, so it stops working for anyone who leaves. Groups that buy ISP together can run a private subnet behind a passcode; Checkout Chefs runs its Australian IPs that way. Rather sell under your own name? That's white-label.
The cook groups pageSubscriptions
254 IPs — Europe
Monthly · renews in 23dIPs
254
Protocol
HTTP
Region
Europe
Renews
23d
Credentials
192.0.2.1:41001:basil_demo:bp7k2v9q4d192.0.2.2:41002:basil_demo:bp7k2v9q4d192.0.2.3:41003:basil_demo:bp7k2v9q4d192.0.2.4:41004:basil_demo:bp7k2v9q4d192.0.2.5:41005:basil_demo:bp7k2v9q4d192.0.2.6:41006:basil_demo:bp7k2v9q4d192.0.2.7:41007:basil_demo:bp7k2v9q4d192.0.2.8:41008:basil_demo:bp7k2v9q4dBot developers
Two APIs. One string format.
The account API hands your bot its balance, usage, orders and ready-made proxy strings on a read-only key, 60 requests a minute. The partner API creates customers, funds them and rotates their credentials. Every string follows one fixed token order, so your parser never has to guess.
The bot developers page# Keep the key in an env var, not in the script curl "https://api.basilproxies.com/api/v1/balance" \ -H "Authorization: Bearer $BASIL_API_KEY"