Genius
Create account

Checkout automation that shows its work.

Genius runs your accounts side by side, headless, and records every run: where it stopped, which attempt, and why.

Create accountSign in
Demo modeSample runs on example.test accounts. No real orders.
Open the demo dashboard
StoreStartSign inFindCartCheckoutOrderLast event
Best Buy UScart and sign-in verified, payment built
Targetreaches checkout entry
Micro Centerreaches guest checkout entry
GameStopreaches guest checkout entry
Costcocart verified, sign-in gate
Walmartchallenge can block the run
Nike and SNKRScart changes denied
Foot Lockercart api blocked by kasada
Neweggreaches guest checkout session
Lowe'sreaches checkout entry
AMD Storereaches checkout entry
Shopify storescheckout entry on one store
Amazoncart verified, sign-in gate
Best Buy Canadaapi endpoints answer, pages not verified
Home Depotcart line not proven
NVIDIA Storeadd denied from datacenter networks
B&H Photo Videoworks when the challenge clears
PlayStation Directadd denied by akamai
Champs Sportscart api blocked by kasada
JD Sportscart api denied
Lines
Verified by self-test
Built, not yet verified
Planned
Blocked by the store
Marks
In motion
Reached checkout
Stopped at a gate
Waiting to retry
Failed or blocked

Lane length is how far each store's pipeline was verified by the engine's own self-tests on 28 September 2026, from one datacenter network. Movement shows the order of stages, not speed.

One run, six stops

Every job moves along the same track, and the run record names the stage where it ended.

  1. Start

    Stages boot, engage

    Event scheduler.started

    Each browser job opens its own throwaway Chrome with no saved profile, through the account's proxy if it has one. Parallel starts are spaced 2 to 15 seconds apart.

  2. Sign in

    Stage login

    Event job.session_ready

    Best Buy accounts sign in with a password, and fall back to an emailed code if that fails. Costco and Amazon need a sign-in that is not built yet, which is why their lanes stop before checkout.

  3. Find

    Stages resolve, availability

    The engine resolves the SKU or product URL and reads availability. If the item is sold out the run ends here, with the stage sold_out.

  4. Cart

    Stages add, cart-read, cart_verify

    Events cart.cooldown_detected, scheduler.cooldown_requeued

    The item is added from inside the page, using the browser's own cookies and fingerprint. Then the cart is read back to confirm the line is really there.

  5. Checkout

    Stage checkout

    For every store except Best Buy US, the pipeline ends at checkout entry or earlier. On Best Buy US it continues through contact, shipping and payment, and a dry run stops before Place order.

  6. Order

    Event scheduler.job_final

    Built for Best Buy US. A dry run goes through payment and stops before Place order. When a job finishes, one record is written and never edited.

Every run ends one of three ways

success
On Best Buy, the confirmation page was detected and the order number is on the record. On every other store it means the cart was confirmed and checkout entry was reached. No order is placed on those stores.
placed_unverified
On Best Buy, Place order was clicked and no confirmation page was detected. The job is never retried, to avoid a double order, so check the retailer account yourself. On other stores it marks a clean run that reached checkout entry. Nothing was placed.
failed
Retries ran out or a cooldown did not lift in time. The record keeps the stage, the attempt and the error text.

A failure that can be retried goes back to Start after a wait, as a new attempt. Waits grow from a 30 second base to a cap of 300.

What a run record holds

Sample record. The account is a placeholder.

task
Main bot
account
buyer01@example.test
stage
login
attempt
3
status
failed
order number
none
error
No verification code delivered within 300s

What works at each store today

20 storefronts are registered. Each entry says how far its pipeline was verified by self-test on 28 September 2026, from one datacenter network.

Verified to checkout entry (7)

These pipelines add to cart, confirm the cart and enter checkout. Payment is not built for any of them.

Target US, general merchandise
Cart adds use store pickup.
Micro Center US, PC components and electronics
Enters guest checkout after the Cloudflare challenge clears.
GameStop US, gaming
Enters guest checkout.
Newegg US, PC components and electronics
Opens a guest checkout session. This module does not use proxies.
Lowe's US, home improvement
Adds through a page navigation, because the cart API is denied.
AMD Store US, processors
Sells processors and a cooler. No graphics cards are listed.
Shopify stores Platform module
13 stores are listed. The pipeline is verified end to end on one, Bodega.

Built through payment (1)

Best Buy US US, electronics
Cart and sign-in are verified. Contact, shipping, payment and Place order are built, and a dry run stops before Place order. Trade-in, gift cards and the tax exempt route are built in.

Stops at a sign-in gate (2)

The cart works. Checkout sits behind an account sign-in that is not built, so a purchase cannot complete.

Costco US, warehouse and general merchandise
No guest checkout exists.
Amazon US, general merchandise
Checkout entry redirects to sign-in. Use the product code, because a search term adds the first result.

Partly verified (6)

Some steps are verified and others are not, or the result depends on a challenge clearing.

Walmart US, general merchandise
The cart contract is captured. A press and hold challenge can block the run before the add.
Nike and SNKRS US, sneakers
Launch feed, availability and size reads are verified. Cart changes are denied from datacenter networks, and draw entries are not built.
Best Buy Canada CA, electronics
The API endpoints answer. Sign-in, cart and checkout pages are not verified.
Home Depot US, home improvement
The flow is built, and a landed cart line is not yet proven.
NVIDIA Store US, graphics cards
Catalog and availability reads are verified. Add to cart is denied from datacenter networks.
B&H Photo Video US, electronics and photo
The full cart chain works when the Cloudflare challenge clears, which is hit or miss.

Blocked from the test network (4)

Product reads work. The cart step was denied by the store's bot defence, so a cart line is not proven.

Foot Locker US, sneakers
Product page, size selection and the add request are verified. The cart API is blocked by Kasada.
PlayStation Direct US, gaming
Search and availability reads are verified. The add request is denied by Akamai.
Champs Sports US, sneakers
Same platform as Foot Locker, with the same limit.
JD Sports US, sneakers
Product lookup works. The cart API was denied on every attempt.

Results on another network may differ. Every store has its own self-test, and you can run it without an account before a drop.

The engine, by its defaults

Values shown are what the engine uses when you change nothing.

Scheduling

Every enabled task is expanded across every enabled account, and each task is parallel or sequential.

Workers
3 at once
Per account
one job at a time
Parallel starts
2 to 15 s apart
Sequential gap
1.5 to 4 s after the previous job

Pacing

One token bucket covers all workers, so adding workers does not multiply the request rate.

Request ceiling
2 per second
Request jitter
300 to 1200 ms

Recovery

A transient block does not end the run.

Retries
3
Backoff
exponential, from a 30 s base, capped at 300 s, with jitter
Best Buy cart cooldown
detected, job queued again
After Place order
never retried

Browser

No windows to watch, and it runs on a machine with no display. Pass --show to see the browser while you debug.

Browser
installed Chrome, new headless mode
Profile
none saved
Cart requests
made inside the page
Challenge pages
waited out, no paid solver

Proxies

Bring your own and pin one to an account.

Format
host:port:user:pass
Order
the account's proxy, then the first stored proxy
Modes
relay, embed, context
Rotation
none

Records

One record per finished job, written once and never edited.

Run history
append only
Logs
one JSON line per event
Failure snapshot
page HTML saved when a Best Buy stage fails
Webhook
the full run record, posted to a URL you set

The record includes the proxy string, so point the webhook only at a URL you control.

A tracker that reports only what changed

Keep a watchlist of products by SKU or product URL. Each snapshot is compared with the one before it, and only four kinds of change are logged. A probe that finds neither a price nor a stock state fails instead of guessing.

npm run track takes one snapshot. npm run watch repeats, every 600 s by default.

Limits

The tracker is separate from checkout. It writes changes to the log, and it does not start runs or send alerts. Use a SKU or a product URL for each watch entry, because a search term can match the wrong product.

  • price_up
  • price_down
  • back_in_stock
  • out_of_stock

event tracker.delta

What you bring, and where it runs

You bring

  • Your retailer accounts and payment details, kept in the engine's files.
  • Your own proxies. None are included.
  • A computer with Node and Chrome installed.
  • For emailed sign-in codes, a connected mailbox, or you paste the code yourself.

Where it runs

The engine runs on your own computer, from the command line or in a desktop window with Dashboard, Tasks, Profiles, Proxies and Settings views. It runs from source. There is no packaged installer yet.

This website is the account side: sessions, tasks, accounts, proxies, run history and a live feed, in any browser, at phone width too.

The engine keeps its run history in a local file. The dashboard shows run records posted to your account through the address in Settings. A built-in link between the two is on the roadmap.

Built today

  • Engine with 20 store entries and a self-test for each
  • Best Buy US pipeline through payment, with a dry run
  • Price and stock tracker with a watchlist
  • Desktop window and command line, run from source
  • Web accounts with run history and a live feed

On the roadmap

  • A link between the engine and the web dashboard
  • Starting and stopping tasks from the web
  • Cloud workers
  • A packaged installer
  • Payment steps for more stores

Only your login can read your rows.

You sign in with an email and a password. Every session, account, proxy, task and run is stored against your user id, and the database returns a row only to the login that owns it.

Proxy strings are stored as you enter them and are masked on screen. Card numbers, security codes and retailer passwords are not collected on this website. They stay in the engine's files on your own computer.

This site loads no analytics script, advertising pixel or session recorder. Fonts and code come from this domain only.

Questions

What does Genius cost?

Pricing has not been announced. Creating an account asks for an email and a password, nothing else.

Does it place orders at every store?

Payment and Place order are built for Best Buy US. Every other pipeline runs through cart and checkout entry today. Stores lists each one.

Does it solve captchas or skip queues?

Challenge pages from Cloudflare, PerimeterX and Akamai are waited out in a real browser and nudged with mouse input. There is no captcha solver, and queues are waited out too.

Are proxies included?

You bring your own. An account's own proxy is used first, and there is no rotation.

Can I start a run from this website?

Runs start in the engine on your computer. The website stores your setup and shows run records. Starting runs from the web is on the roadmap.

Does it work outside the United States?

Every store entry targets the US storefront except Best Buy Canada, which is registered and not verified.

How do emailed sign-in codes work?

For a Best Buy account without a password, the engine asks Best Buy to email a code and types it in when the code reaches a connected mailbox. If your mailbox is not connected, run with --assist-codes and paste the code.

Do I have to confirm my email?

Yes. After you create an account we send a confirmation email. Sign in works once you follow the link in it.

Will I get alerts?

Finished runs can be posted to a webhook you set, and tracker changes are written to the log. Discord, SMS, email and push alerts are not built.

Is there an installer?

Not yet. The engine runs from source today, and a packaged installer is on the roadmap.

Get access

  1. Enter an email and a password.
  2. Open the confirmation email and follow the link.
  3. Sign in. Your dashboard starts empty, ready for a first session.

Sign in works only after the email is confirmed.

Create accountSign in