Residential proxies for sneaker bots

Monitors: rotating IPs

Stock and drop monitors make many small, independent requests. Point them at the rotating port 9000 so each request uses a new IP, and keep the polling interval reasonable for the store you're watching.

Checkout tasks: one sticky session each

A checkout flow sets cookies and expects them to come back from the same IP. Give every task its own session id on port 10000, with a lifetime long enough to cover the release window (1 to 1440 minutes). Choose IPs in the store's region, down to state or city, so the session sees the same regional storefront as the store's local customers.

# host:port:user:pass, one line per task
gw.nodelighthouse.com:10000:<USERNAME>-type-residential-country-us-state-ca-city-losangeles-lifetime-30-session-task0001:<PASSWORD>

Import a list into your bot

The dashboard proxy generator exports up to 1000 lines at once, each with its own sticky session, in host:port:user:pass, user:pass@host:port or http:// format. Copy the list or download it as a .txt and paste it into your bot's proxy settings. See the bot proxy list guide.

Respect each store's rules

Many retailers set purchase limits per customer, use raffles, or don't allow automated checkout at all. Only run checkout tools you are permitted to use on a given store, and follow its release rules. Proxies don't change what a store allows. See the acceptable use policy.

Setup guides

• Bot proxy lists
• cURL

Questions

How many proxy lines can I generate?

Up to 1000 lines per export from the dashboard proxy generator, each with its own sticky session.

How long does a sticky session last?

As long as you set in the username: any lifetime from 1 to 1440 minutes.

Is bandwidth billed per proxy line?

No. You pay for bandwidth only, at a flat $1.65/GB, no matter how many lines you generate.