Exchanges
CubeTerminal connects to five live perpetual futures venues, with a sixth (Arcus) integrated and coming soon. Each has its own connection model, and you can run all of them at once — the active exchange selector in the header decides which one receives orders from the Trade Entry widget, the Command Line, and the Telegram bot.
Supported venues
| Exchange | Products | Auth model | Notable |
|---|---|---|---|
| Hyperliquid | Perps | Agent wallet (on-chain) | Fully on-chain, popup-free signing, no API key |
| Bybit | Perps (USDT-M + USDC + inverse) + dated futures | API key + secret | Builder-dex tickers (xyz:TSLA), v5 API |
| Binance | USD-M Perps | API key + secret | Largest liquidity, IP allowlist recommended |
| Bitget | USDT-M Perps | API key + secret + passphrase | Passphrase is mandatory and unique to Bitget |
| Phoenix | Perps (Solana on-chain) | Wallet sign-in | Fully on-chain, isolated margin per market, no API key |
| Arcus (coming soon) | Perps (crypto + stock perps) · spot data | One-time wallet signature → local signing | Robinhood Chain, TSLA/NVDA/SPY perps, popup-free orders |
Arcus is integrated but not yet live. The venue ships dormant (a "Soon" badge in the exchange list) until Arcus opens its perps publicly. Everything below applies to the five active venues; the Arcus guide documents what will work at launch.
Spot trading in CubeTerminal happens via the Swap widget, which routes through Jupiter (Solana) and 0x (EVM) directly from your terminal wallet. Centralised-exchange spot books are not connected. When Arcus goes live, its spot stock tokens stream as live data in the Symbols widget; trading them happens in the Arcus app.
Choosing an exchange
- Hyperliquid — pick this if you want self-custody and no API key management. Your funds stay in your own wallet; the terminal signs orders with an agent wallet that only has trade permission.
- Bybit — pick this if you want deep liquidity on both crypto perps and builder-dex equity perps (Tesla, Apple, MSFT, etc.) via the
xyz:prefix. - Binance — pick this for the broadest symbol universe and tightest spreads on major pairs. USD-M futures only.
- Bitget — pick this for USDT-M futures with competitive maker rebates. Note the extra passphrase field when creating the API key.
- Phoenix — pick this for fully on-chain Solana perps with isolated margin per market and USDC settling straight to your wallet.
- Arcus (coming soon) — stock perps (TSLA, NVDA, SPY, …) alongside crypto with Hyperliquid-style popup-free signing on Robinhood Chain. Integrated but not yet selectable — see the Arcus guide.
Connecting
All exchange credentials live in Settings → Trading Accounts. Every connection is local — credentials and signing keys are stored in the terminal's encrypted storage and never transmitted anywhere except to the exchange's own API endpoints.
Each per-exchange guide walks through the specific setup:
- Hyperliquid connection guide — on-chain flow with agent wallet
- Bybit connection guide — API key + secret
- Binance connection guide — API key + secret
- Bitget connection guide — API key + secret + passphrase
- Phoenix connection guide — Solana wallet sign-in
- Arcus connection guide — one wallet signature, then local signing
Never grant withdrawal permission to an API key you paste into any third-party tool, including CubeTerminal. Read + Trade is all the terminal needs. The wallet-based venues (Hyperliquid, Phoenix, Arcus) follow the same principle by design — their trading keys cannot withdraw.
Sub-accounts
All six venues support some form of sub-accounts:
- Hyperliquid — create sub-accounts on the Hyperliquid web UI, then authorize the agent wallet from each sub-account you want to trade from.
- Bybit / Binance / Bitget — generate a separate API key pair inside each sub-account and add it as a second connection in Trading Accounts.
- Phoenix — per-market isolated subaccounts are automatic; each market funds its own subaccount on first trade.
- Arcus — one address holds up to ten account indexes (0–9); the terminal trades index 0 by default.
Balances and positions from every connected key show up in the Accounts widget.