Quick Start Guide
Get up and running with TokenBot in under 5 minutes.
Step 1: Get access
Section titled “Step 1: Get access”TokenBot is currently early access — there is no self-serve signup. Join the waitlist at site.tokenbot.com; you’ll be told when your account is ready.
You need an account before the CLI is useful: tokenbot init binds a key to an existing account,
it does not create one.
Step 2: Install the CLI (1 minute)
Section titled “Step 2: Install the CLI (1 minute)”TokenBot is CLI-first — there is no web dashboard. Requires Node.js 22+:
npm install -g tokenbotStep 3: Register your CLI identity (1 minute)
Section titled “Step 3: Register your CLI identity (1 minute)”tokenbot init --label "my laptop"tokenbot whoamiinit generates a secp256k1 keypair, encrypts it under a passphrase you choose, and registers the
public key against your account. Every later request is signed with that key — no API key, no
password sent anywhere. whoami confirms it worked.
Step 4: Connect an exchange (3 minutes)
Section titled “Step 4: Connect an exchange (3 minutes)”First, at your exchange (e.g. Binance), create an API key:
- Enable: read + trade permissions
- Disable: withdrawal permissions — do this every time, without exception
Then pick the path that matches what you want:
# Server-side: TokenBot can trade for you (needed for copy trading)tokenbot exchange add --exchange binance --account-name "main" --trading-type spot# Local-only: credentials never leave your machine; used by `tokenbot balance`tokenbot keys add --exchange binance --strategy strat_9fThese are deliberately separate. exchange add uploads credentials to the server so the platform can
act on your behalf; keys add stores them encrypted in ~/.tokenbot/keys.json and never transmits
them. See Exchange Accounts.
Step 5: Set up copy trading (1 minute)
Section titled “Step 5: Set up copy trading (1 minute)”A Copier follows a Strategy:
# See the strategies available to followtokenbot strategy list
# Create a copier against one, allocating 25% of your exchange accounttokenbot copier add --strategy strat_9f --exchange-account-id exa_71 --name "btc follow" --allocation 25
# Confirm the bindingtokenbot links listStep 6: Watch it work
Section titled “Step 6: Watch it work”When the strategy you follow fills a trade, TokenBot detects the fill on the leader’s exchange account and fans it out to your copiers.
tokenbot tradesOptional: Set Up Webhooks
Section titled “Optional: Set Up Webhooks”Send real-time trade notifications to any HTTPS endpoint — Discord bots, Telegram alerts, or your own systems:
tokenbot webhooks add --url https://example.com/hooks/tokenbot --events trade.filledtokenbot webhooks test <id>See Webhooks → for details.
For Developers
Section titled “For Developers”Prefer working from the command line or building integrations? TokenBot has you covered.
CLI Quick Start
Section titled “CLI Quick Start”Requires Node.js 22+. The user CLI is published to public npm as tokenbot (unscoped):
npm install -g tokenbot
tokenbot init --label "my laptop"tokenbot whoamiinit generates an encrypted identity keypair and registers it. You are not asked for an API
key — the CLI signs every request with your private key, which never leaves your machine.
See CLI Installation → for full setup instructions.
SDK Quick Start
Section titled “SDK Quick Start”The SDK is a TypeScript package on GitHub Packages. It authenticates with the same signed-request identity the CLI uses, not an API-key string:
npm install @tokenbot-org/sdk @tokenbot-org/cli-coreimport { SignedHttpClient, unlockIdentity } from '@tokenbot-org/cli-core';import { TokenbotSdk } from '@tokenbot-org/sdk';
const privateKey = unlockIdentity(encryptedKey, salt, passphrase);const http = new SignedHttpClient({ apiUrl: 'https://api.tokenbot.com', publicKey, privateKey });
const sdk = new TokenbotSdk({ http, graphqlUrl: 'https://gql-api.tokenbot.com/graphql', wsUrl: 'wss://gql-api.tokenbot.com/graphql', // only needed for *Watch subscriptions});
const strategies = await sdk.strategies.list();There is no Python SDK. The standalone Python and Node SDK repositories were retired on 2026-06-28;
@tokenbot-org/sdkis the only supported client library.
See SDK Overview → for full documentation.

