Botsupply
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port the process listens on. The process binds 0.0.0.0. | 4317 |
| SQLITE_PATH | No | Path to the SQLite database file. If set, it is used as-is. Otherwise the file is /data/botsupply.sqlite when /data is writable, otherwise ./data/botsupply.sqlite. | |
| PUBLIC_BASE_URL | No | Public base URL for the service, e.g. https://botsupply.onrender.com. Required for paid Stripe checkout when Stripe is enabled. | |
| STRIPE_SECRET_KEY | No | Secret key from Stripe (sk_test_… or sk_live_…). When set together with STRIPE_WEBHOOK_SECRET and PUBLIC_BASE_URL, the DEV top-up route returns 403 and agents pay with Stripe Checkout. | |
| STRIPE_WEBHOOK_SECRET | No | Signing secret for the Stripe webhook endpoint (whsec_…). Required for paid Stripe checkout when Stripe is enabled. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_catalogA | List live BotSupply SKUs, credit prices, short descriptions, and what a purchase does not include. Payloads stay behind purchase. recipe.book-table, when listed, is recipe documentation only and does not place a reservation. |
| open_walletA | Create a wallet and return wallet_id plus api_key once, with balance_credits 0. Same as POST /v1/wallets. This does not look up an existing wallet. Keep the api_key; later tools need it as Authorization: Bearer or as api_key. |
| get_balanceA | Return the authenticated wallet id and prepaid credit balance. Same as GET /v1/balance. Does not return the API key. |
| purchaseA | Buy one live catalog SKU with prepaid credits. Sends { sku } to POST /v1/purchase and returns that JSON, including the pack or recipe payload. Does not place a reservation. recipe.book-table is documentation the buying agent runs itself. An unknown SKU is rejected. Insufficient balance returns an error and does not deduct credits. |
| create_checkoutA | Start a Stripe Checkout credit top-up. Same as POST /v1/wallets/:id/checkout. Returns the checkout url (open that URL; it keeps Stripe's hosted-page fragment). credits is an integer from 100 to 100000. Credits are applied only after Stripe reports the session paid. Returns the API error when Stripe is not configured. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool maps to a distinct action+resource: create a wallet, read balance, browse the catalog, spend credits (purchase), and top up credits (create_checkout). The purchase vs. create_checkout pair is the only adjacency, and their descriptions explicitly separate 'spend prepaid credits on a SKU' from 'start a Stripe top-up session', so misselection is unlikely.
Four of five names follow a clean verb_noun snake_case pattern (open_wallet, get_balance, list_catalog, create_checkout). 'purchase' breaks the pattern as a bare verb with no noun, and 'open_wallet' uses a different verb than the sibling 'create_checkout' for a create action, but overall the set reads consistently.
Five tools is a tight, well-scoped surface for a wallet/credits/catalog flow with no redundant endpoints. It is slightly thin (no history or lookup operations), which keeps it just under ideal rather than excessive.
The core lifecycle is covered: create wallet, check balance, list SKUs, purchase, and top up credits. Minor gaps remain — no transaction/purchase history, no way to recover a lost api_key, and no refund or wallet-management operations — but agents can complete the primary buy-credits-then-purchase workflow.