botx402 in Claude.
A reorder plan from your chat.
Add one connector, no sign-in. Claude checks your inventory data for free, hands you a Stripe link to pay $19.00 when it's ready, and brings the plan back into the conversation.
https://api.botx402.io/mcp
What it does
The botx402 connector lets Claude (or any MCP client) run botx402 bots for you. Today that is Inventory Reorder Snapshot: give it your SKU sales history, stock on hand, open orders and supplier lead times, and it returns a reorder plan — what to order now and how many, what is out of stock or about to run out, what is overstocked or not selling, how much cash is tied up, and which SKUs earn the revenue. You get a PDF report and a JSON plan your assistant can act on.
It is rule-based and deterministic, computed only from the figures you supply. It is not a forecast: it does not model seasonality, trends or promotions, multiple locations, variant roll-ups, supplier price breaks or margin, and it does not connect to Shopify or any other system.
The connector never charges anyone. Starting a run returns a Stripe checkout link that you open and pay yourself ($19.00 per run). Nothing runs until you do.
Set up
In Claude: Settings → Connectors → Add custom connector. Name it "botx402", enter the URL https://api.botx402.io/mcp, and choose No sign-in. On Team and Enterprise plans an owner adds it under Organization settings → Connectors, and members then connect.
There is no account and no API key. The server speaks Streamable HTTP; leave Claude's transport setting as it is.
Other MCP clients: add a remote (Streamable HTTP) server with the same URL, no authentication.
How a run works
1. list_bots — what each bot does, its price, its input schema. Free.
2. validate_inventory_reorder_inputs — checks your data and lists every problem at once, each with where it is (for example inputs.skus[3].lead_time_days) and how to fix it. Free; nothing is stored or charged. Claude fixes what it can and asks you about the rest.
3. start_inventory_reorder — with the same data plus your email address, creates a Stripe checkout and returns the link, a receipt ID and an access token. It never charges anyone; you open the link and pay by card.
4. get_run — once you have paid, Claude checks the run with the receipt ID and access token. When it is complete (usually within a few minutes of payment) it gets the full JSON plan and a link to the PDF. You also get an email with your results link.
The access token is what proves a run is yours: without it, get_run returns nothing. The same token is in the results link Stripe sends you back to.
Example prompts
"Here's my stock export and last 90 days of sales [attach CSV]. What should I reorder this week, and how many units?"
"Which of my products are overstocked, and how much cash is tied up in them? Lead time is 21 days for everything."
"Check whether this inventory data is good enough for a reorder plan before I pay for one."
"Run a reorder plan on this sheet and then draft purchase orders for the SKUs marked reorder now."
Pricing
$19.00 per run, paid by card through Stripe Checkout. Checking your data (validate) is free, as many times as you like. No subscription.
A run that fails is refunded automatically.
Limits
Up to 800 SKUs per run, and the whole request must stay under 200 KB. Sales history window of 28 to 365 days (default 90).
Each SKU needs sku, units_sold, on_hand, unit_price and unit_cost; lead_time_days per SKU or as a default for all.
Up to 10 checkouts per email address per day through the connector.
Checkout links expire after 24 hours. Download links last 7 days (your results link makes a fresh one), and reports are kept for 90 days.
Very large plans: Claude receives the SKUs that need action (reorder now, out of stock, stockout risk, overstock) plus the summary, with a link to the full JSON.
Privacy
Validate stores nothing. Starting a run stores your validated data until you pay (deleted after a day if you don't), and your email on the run record. We never log your data, your email or your access token. Full details: botx402.io/privacy, section 03.
Troubleshooting and support
"Not valid yet": every listed problem has a path and a fix; correct them and validate again.
"No run matches": get_run needs the exact receipt ID and access token from the start step.
"Awaiting payment" after paying: wait a minute and check again. Still stuck, or anything else: email hello@botx402.io with your receipt ID. Security reports to the same address.