botx402 MCP Server

List the bots this server can run: what each one does, its price per run, what a run returns, its input schema, and the names of its validate_ and start_ tools. Free and read-only.

Check a run started with a start_ tool and fetch its results. Needs the receipt_id AND the access_token that start_ returned: the token is the proof that the caller started the run, and without it nothing is returned. Status is awaiting_payment (the user has not paid yet), running, completed or failed. When completed, structuredContent.result is the bot's full JSON result, ready to act on, and pdf_url links the PDF report (presigned, expires after 7 days). Free and read-only; poll about once a minute.

Start a paid Inventory Reorder Snapshot run ($19.00 per run). This tool never charges anyone; it returns a Stripe checkout link that a person opens and pays. It creates the checkout and returns the link with a receipt_id and access_token. Nothing runs until the person pays on Stripe's page. Show the user the link and the price and ask them to pay; then call get_run with the receipt_id and access_token. Results are also emailed to the address given. Takes the same JSON as validate_inventory_reorder_inputs ({"inputs": {...}, "email": "..."}); run validate_inventory_reorder_inputs first, since invalid inputs are rejected here too. Each call creates a new checkout, so do not retry a call that succeeded. Returns: A PDF report and a JSON plan: one row per SKU (status, order quantity, days of cover, cash tied up) plus summary totals. Turns a store's per-SKU sales history, stock on hand, open purchase orders and supplier lead times into a reorder plan: which SKUs to reorder now and how many units (rounded up to MOQ and case pack), which are out of stock or will run out before the next delivery could arrive, which are overstocked or not selling, how much cash is tied up in excess stock, and which SKUs earn the revenue (ABC tiers). It is rule-based and deterministic, computed only from the figures supplied. It is not a forecast: it does not model seasonality, trend or promotions, multiple locations, variant roll-ups, supplier price breaks or margin. It does not connect to Shopify or any other system; the data is sent inline. Inputs: an as_of date, an optional window_days (28 to 365, default 90) that units_sold covers, and 1 to 800 SKUs, each with sku, units_sold, on_hand, unit_price and unit_cost. lead_time_days is needed per SKU or in defaults. The whole request must stay under 200 KB.

Check inputs for Inventory Reorder Snapshot before asking a human to pay. Free; nothing is charged, stored or run. Takes exactly the JSON start_inventory_reorder takes: {"inputs": {...}}, plus "email" if you have it (checked too, optional here). Returns either valid (with a one-line summary of what will be analysed) or every problem found at once, each with its path (e.g. inputs.skus[2].unit_cost) and how to fix it. Fix them all, call again, then call start_inventory_reorder with the same JSON plus the buyer's email. Turns a store's per-SKU sales history, stock on hand, open purchase orders and supplier lead times into a reorder plan: which SKUs to reorder now and how many units (rounded up to MOQ and case pack), which are out of stock or will run out before the next delivery could arrive, which are overstocked or not selling, how much cash is tied up in excess stock, and which SKUs earn the revenue (ABC tiers). It is rule-based and deterministic, computed only from the figures supplied. It is not a forecast: it does not model seasonality, trend or promotions, multiple locations, variant roll-ups, supplier price breaks or margin. It does not connect to Shopify or any other system; the data is sent inline. Inputs: an as_of date, an optional window_days (28 to 365, default 90) that units_sold covers, and 1 to 800 SKUs, each with sku, units_sold, on_hand, unit_price and unit_cost. lead_time_days is needed per SKU or in defaults. The whole request must stay under 200 KB.