Choose the connection that fits your account.
Schizo Terminal is a trading interface for exchange accounts you already hold. Connection coverage is specific to the provider, market type and environment. A familiar exchange logo in an account selector does not confirm that every action has completed release review.
| Connection | Current release coverage | Before connecting |
|---|---|---|
| Bybit derivatives | USDT and USDC linear contracts, plus coin-settled inverse contracts. Live and Demo use their matching credentials. | Combined inverse trading requires a verified UTA 2.0 account. |
| Bybit Spot | A separate Spot connection is present in the terminal. | Separate release review; it is not included in the combined derivatives claim. |
| Other exchange integrations | Further integrations are being reviewed. | Provider-specific public release information will be added after verification. |
The next connections are under review.
OKX, Kraken, Hyperliquid, Binance, Bitget, Lighter and BloFin are in the integration pipeline alongside Bybit. We will publish provider-specific coverage and setup pages as each connection completes release verification.
This is a development roadmap, not confirmation that those accounts can already execute every supported workflow. The released coverage table above is the current reference.
Different connections, clear context.
Give each connection a name that identifies its exchange and purpose. When more than one is active, use the account selector or a split chart’s connection selector to choose the context. The Place Order module should show the intended account and instrument before an instruction is submitted.
Multiple-account workflows and split-chart selection explain how this works. Adding multiple connections does not automatically duplicate orders across them.
Prepare the key and verify the connection.
Create credentials in your exchange’s API-management screen. Match the environment and grant the read/trade permissions required for the workflow. Withdrawals are not required. Keys with an IP allowlist must permit the deployment’s exchange-relay addresses.
Follow the connection guide, then confirm private balances, positions or orders. Permissions, account eligibility, supported products and exchange limits remain provider-specific.
Credentials are stored encrypted on your device. Signing happens on the device; signed requests, API-key identifiers and responses pass through the exchange relay in memory. See data handling for the full explanation.