Bot Operator CLIs
Advanced. Alongside the main tokenbot CLI, each automated engine ships its own operator CLI for working with that engine directly: tokenbot-mm for the market-maker and tokenbot-trading for the trading bot.
These are embedded with their respective bot services (the bots themselves run as scheduled AWS Lambda cycles). The operator CLIs reuse the same encrypted identity and local-key model as the main tokenbot CLI — run init once to register a CLI identity, then keys add to store local exchange credentials in ~/.tokenbot.
Most users never need these. Reach for them only if you operate a bot engine directly.
What changed in July 2026: the engines' dashboard-era HTTP APIs — and the
/v1/trading-bot/*//v1/market-maker/*REST proxies in front of them — have been removed (they were never wired up in any deployed environment). The operator CLIs now work exclusively through the central platform APIs (api.tokenbot.comREST andgql-api.tokenbot.comGraphQL), with live streams over the signed graphql-wstradeSignal/orderbookUpdatesubscriptions. Remote engine control (pause / resume / emergency-stop) went with that surface and returns in a future signed control-plane wave.
Both CLIs share these global options:
--json
Emit machine-readable JSON instead of tables
--config <path>
Use an alternate config directory (sets TOKENBOT_HOME) instead of ~/.tokenbot
--version
Print the CLI version
--help
Show help for any command
tokenbot-mm — Market-Maker Operator
Operator surface for the market-maker engine, which runs a quoting cycle every ~5 minutes.
Setup
tokenbot-mm init
Generate a CLI identity and register it with TokenBot. Options: --api-url <url>, --ws-url <url>, --label <label>
tokenbot-mm keys add
Add or replace an exchange API credential (stored locally, never sent to the server). Requires --exchange <name>
tokenbot-mm keys list
List stored credential labels
tokenbot-mm keys remove --exchange <name>
Delete the stored credential for an exchange
tokenbot-mm balance --exchange <name>
Fetch exchange balance locally via CCXT
Live order book
tokenbot-mm orderbook watch --exchange <id> --symbol <pair>
Stream live order-book snapshots (top-N bids/asks plus a freshness read-out) over the signed graphql-ws orderbookUpdate subscription until Ctrl-C. Option: --depth <n> (default 10)
Removed commands:
status,config show/set,pause,resume,emergency-stop,spreads adjust,inventory,analytics, and the one-shotorderbook showwere removed in the July 2026 prune — they depended on the market-maker's dashboard-era HTTP API, which never had a live backend. Engine control returns via the future signed control plane.
tokenbot-trading — Trading-Bot Operator
Operator surface for the trading engine, which runs a strategy cycle every ~15 minutes.
Setup
tokenbot-trading init
Generate a CLI identity and register it with TokenBot. Options: --api-url <url>, --ws-url <url>, --label <label>
tokenbot-trading keys add --exchange <name>
Add or replace the trading-bot exchange credential (stored locally)
tokenbot-trading keys list
List stored credential labels
tokenbot-trading keys remove --exchange <name>
Delete the stored credential (double-confirms)
tokenbot-trading balance --exchange <name>
Fetch exchange balance locally via CCXT
Strategies
tokenbot-trading strategy list
List all strategies registered for this account
tokenbot-trading strategy show <id>
Show a single strategy as JSON
tokenbot-trading strategy add
Create a new strategy (interactive). Options: --name, --description, --exchange-account-id
tokenbot-trading strategy enable <id>
Enable a strategy (takes effect on the next 15-minute tick)
tokenbot-trading strategy disable <id>
Disable a strategy (takes effect on the next 15-minute tick)
Activity
tokenbot-trading signals watch
Stream live trade signals over the signed graphql-ws tradeSignal subscription until Ctrl-C. Option: --strategy <id>
tokenbot-trading trades
List recent trades. Options: --strategy <id>, --symbol <pair>, --status <status>, --limit <n>
Removed commands: the one-shot
signalslisting,positions,backtest run/results, andemergency-stopwere removed in the July 2026 prune — they depended on the trading bot's dashboard-era HTTP API, which never had a live backend. Emergency-stop and other remote controls return via the future signed control plane.
Next Steps
The everyday user CLI: The TokenBot CLI →
How the engines fit together: How It Works →
Last updated
Was this helpful?

