Nvidia

Complete guide on our Nvidia module

Nvidia uses guest checkout for GPU releases and restocks. Stock can sell out quickly, so prepare your profile, product ID, proxies and captcha setup ahead of time. A correct setup does not guarantee a successful order.

Quick Start — Recommended Setup

1. Create a Nvidia task group in Tasks and click Create Task.
2. Choose normal, select your profile, and choose monitoring and checkout proxy groups. Enter the correct PID for the product.
3. Keep Product Quantity at 1 unless the listing allows more and you intend to buy more. Set Max Price to your acceptable price per item.
4. Choose a Captcha Provider and complete its setup before starting. Bot uses a Chrome captcha harvester; the other choices need their corresponding service configured.
5. For random restocks, add a Monitor task for the same PID and enable Watch Task on Normal. For a timed release, Normal can run independently with Watch Task off.
6. Start with the current default Delay of 3000 ms, then adjust using the delay guidance below. Set the bottom Qty to the number of task rows and click Create. Review before starting: Normal can place orders.

Preliminary Checklist

Prepare your profiles with accurate billing, shipping and payment information.

Use high-quality ISP or residential proxies and keep another pool available. Flagged or unsuitable proxies can cause Akamai errors. A fast proxy test does not guarantee that Nvidia will accept the proxy.

For proxy options, see Stella Proxies.

Use your cook group to confirm the current PID and release timing.

Prepare the captcha option selected in the task. If testing on an in-stock product, only start Normal when you intend to purchase it; a test checkout can place a real order.

Accounts & Sessions

Normal uses guest checkout with the selected profile. The current form has no Account or Session field, so there is no separate saved-account login setup.

Captcha Harvesters & Providers

A captcha is a verification challenge from the retailer. Normal needs a way to solve it before checkout can continue. A captcha harvester is the window used to display challenges when Bot is selected.

Bot: follow the Captcha Harvester setup guide. Google Chrome is required. Create and open a harvester in Harvesters → Captcha Harvesters, select Bot in the task, and be ready to solve the challenge.

AYCD: follow the AYCD setup guide, keep AutoSolve connected, and choose Aycd in the task.

Capsolver: follow the CapSolver setup guide. Configure its key and balance before selecting Capsolver. The existing guide recommends it as an automatic third-party option.

Capmonster: follow the CapMonster setup guide and configure its key and balance before selecting Capmonster.

Choose one provider for each task. A valid key or balance alone does not guarantee a solve; the task must reach a supported captcha challenge and the selected service must be working.

Supported Modes

• normal: attempts guest checkout. With Watch Task enabled, it waits for a matching Monitor signal; otherwise it checks the product itself.
• monitor: checks stock for a PID and signals matching Normal Watch Tasks. It does not place orders.

Normal Mode

Use normal to purchase the product with your saved profile.

• Name: optional task label.
• Mode: choose normal.
• Profile: select the saved checkout information.
• Monitor Proxy: choose the proxy group for the task’s stock checks.
• Checkout Proxy: choose the proxy group for checkout requests.
• PID: the product identifier. Use the correct PID for your intended product and region; see the example below.
• Product Quantity: units to attempt in each order. The default is 1. Follow any listing or release limit.
• Max Price: maximum acceptable price for one unit, even when Product Quantity is greater than 1. It is not your total order budget; allow separately for tax and shipping.
• Captcha Provider: Bot, Capsolver, Capmonster or Aycd. Complete the matching setup above.
• Delay: retry interval in milliseconds. The current default is 3000 ms, or 3 seconds.
• Watch Task?: enable to wait for a matching Monitor task. Leave off for independent Normal tasks.
• Start Time and End Time: optional scheduling controls.
• Qty at the bottom: number of task rows to create. This is separate from Product Quantity.

Monitor Mode

Use monitor to check stock and trigger matching Normal Watch Tasks.

• Name: optional task label.
• Mode: choose monitor.
• Profile: an optional profile selector is shown. Monitor checks stock and does not purchase.
• Monitor Proxy: select the group used for stock checks.
• PID: use the same product identifier as the Normal tasks you want to trigger.
• Delay: interval between stock checks in milliseconds. The current default is 3000 ms.
• Reset Delay: pause after detecting stock before monitoring again. The field starts blank. The existing recommendation is 5000–10000 ms, or 5–10 seconds.
• Start Time and End Time: optional scheduling controls.
• Qty at the bottom: number of Monitor task rows to create.

Finding the PID

The easiest option is to get the correct PID from your cookgroup. Confirm it matches the product and region you intend to run.

The existing manual method is to open the product page’s HTML source, search for data-pid, and copy the numeric identifier without commas. If that value is missing or unclear, ask your release source rather than guessing.

The existing example is the Nvidia GeForce RTX 5090 product page with PID 1149380. This is an example identifier, not a guarantee that the product is currently available.

Example: Monitor + Normal

1. Create a Monitor task with the intended PID, monitoring proxies and suitable delays.
2. Create a Normal task with the same PID, your profile, proxies, Product Quantity 1, Max Price and configured captcha provider. Enable Watch Task.
3. Start both. Monitor checks stock and signals Normal to attempt checkout. Be ready for captcha challenges if using Bot.

For timed releases, follow the release setup and use Normal with Watch Task off when running independently. Watch Task can reduce repeated checkout-side stock checks, but it does not guarantee that proxies will avoid blocks.

FAQ

Which delays should I use?

The current forms default to 3000 ms. The existing guide suggests 6000–9000 ms for restocks, 3000–5000 ms for releases, and 5000–10000 ms for Reset Delay. Use these as starting ranges, then adjust to proxy performance and current release guidance. Lower delays make more requests and do not guarantee success.

Which proxies should I use?

The existing recommendation is high-quality ISP or residential proxies. See the original Stella Proxies resource for options. Keep alternatives available because performance varies by pool and release.

Is Qty the number of products or tasks?

Product Quantity is the number of units per order. Qty at the bottom creates task rows. Several Normal rows may each place an order, so review both before starting.

Common Errors & Troubleshooting

Waiting for captcha or no solve

Check which provider the task actually uses. For Bot, make sure Chrome is installed and a captcha harvester is open. For AYCD, check the AutoSolve connection. For Capsolver or Capmonster, check the configured key, remaining balance and service response. If it still fails, send support the exact task status and provider name without sharing the API key.

Akamai errors or blocked requests

Check proxy credentials, try another suitable pool and increase the delay if needed. Also check for current Stellar updates or retailer issues. Repeatedly restarting a blocked setup is not a guaranteed fix.

Normal keeps waiting

With Watch Task enabled, confirm a Monitor is running for the same PID. If you intended Normal to run independently, leave Watch Task off.

Product not found or price rejected

Confirm the PID, region and actual stock. Check Max Price against the product’s current price. Only increase it if you are willing to pay that amount per unit.

Checkout fails

Review the profile and listing purchase limits. Record the exact error, mode and PID for support; do not include payment details or service keys.

---