Adding Exchange API Keys

Ionide currently supports Bitget and MEXC. Your API key lives on your own bot instance, encrypted at rest — it's never sent to any Ionide-operated service.

The rule: trading yes, withdrawals never

Ionide only needs trading permissions to place spot and futures orders. It never needs, and will never ask for, withdrawal permissions. If the exchange's key form has a withdrawal toggle, leave it off.

Bitget

1. Go to API Management in your Bitget account settings.
2. Create a new key and enable Spot Trading and Futures Trading permissions.
3. Leave Withdraw unchecked.
4. Bitget also requires a passphrase you set when creating the key — keep it, you'll need it below.

MEXC

1. Go to API Management in your MEXC account settings.
2. Create a key and enable Spot Trading and/or Futures Trading, matching what you plan to run.
3. Leave Withdraw unchecked.
4. MEXC's spot and futures API keys are separate — you'll store them separately with /secrets-set (see below).

Storing the key in Discord

Run /secrets-set in your command center channel and choose the exchange:

• bitget — needs API key, secret, and passphrase.
• mexc-spot / mexc-futures — needs API key and secret (no passphrase).

The bot encrypts what you enter and stores it locally; values are never echoed back, not even to you. Check what's configured with /secrets-status, and verify a key actually works — including confirming it has no withdrawal permission — with /secrets-test.

Rotating or revoking a key

Revoke a key from your exchange's dashboard at any time — the bot will fail to place new trades on that account but won't touch existing open positions. Run /secrets-set again with a new key to replace it, or /secrets-remove to clear it.

Something look wrong?

If a key stops working, re-run /secrets-test — it'll tell you if the key is invalid, expired, or missing a required permission. Reach out on Discord if you're stuck.