Connections
Connections supply market data and, where explicitly supported, create account routes for local simulation or provider trading.
See Feature And Provider Status before configuring a provider. A provider name in the application does not by itself mean that live account routing is available.
The connection that supplies chart data and the account selected for orders are separate choices. Playback does not select LocalPaper automatically. In the current release-candidate build, HyperionX rejects submissions, changes, and cancellations for selected Broker and Server Paper accounts while Playback is active; select LocalPaper for replay trading.
Public Provider Matrix
| Provider surface | Status | Historical/live data | Market depth | LocalPaper | Provider account and order route |
|---|---|---|---|---|---|
| KuCoin | Current; release certification still required | Spot and Futures, subject to enabled markets | Yes | Yes | Account reads and Broker routing require validated manual API-key or linked-account permissions. Spot and Futures capabilities can differ. Release-enabled Local Agent live routing adds a separate default-off setting and account/instrument scope checks. |
| Rithmic | Current; release certification still required | Yes, subject to environment and entitlements | Yes | Yes | Broker accounts and routing are available with valid credentials and configuration. A connection can expose multiple account identities. |
| Hyperliquid data | Current | Yes | Yes | Yes | Market-data access does not enable live wallet trading. |
| Hyperliquid wallet trading | Preview; unreleased for general live use | Uses the Hyperliquid data connection | Yes | N/A | Requires a connected external wallet, locally generated agent key, agent approval, and builder-fee approval. Local Agent live routing requires additional release, capability, setting, entitlement, account, and risk gates. |
| Binance | Unavailable / Coming Soon | No supported clean-setup path | No supported clean-setup path | No | The connection picker locks new setup. Legacy preconfigured state is not release-certified. |
| Jupiter Exchange | Unavailable | No supported public integration | No | No | Placeholder only. |
| o1.exchange | Unavailable | No supported public integration | No | No | Placeholder only. |
| Tradovate | Unavailable | No supported public integration | No | No | Placeholder only. |
DxFeed, Interactive Brokers, and CQG are not enabled in the supported connection picker. Treat their adapter code as internal or legacy, not as public provider support.
Account Modes
| Mode | Current behavior |
|---|---|
| Broker | External provider account. Orders can affect real capital. |
| Server Paper | Provider-managed non-live account where the provider exposes one. |
LocalPaper / Hyperion Sim | Local simplified simulation driven by the connection's market updates. |
| Playback | Historical replay clock and data source. It does not change the selected account, but the current release-candidate build blocks Broker and Server Paper order mutations while Playback is active. Use LocalPaper for replay trading. |
| Data only | Historical/live market data without a supported external account route. |
Read Accounts And Trading Environments before combining Playback, a live connection, and an order-entry surface. The Playback guard is a backstop, not a substitute for verifying the selected account.
Provider Capabilities
KuCoin
KuCoin can load Spot and Futures independently. Public capabilities include historical/live data, streaming depth, account state, order routing, order change/cancel behavior, and client-order-identifier reconciliation when the selected authentication mode and permissions allow them.
Manual API keys require the appropriate read and trading permissions. A linked account can be read-only or trading-enabled. Do not assume Spot permission grants Futures permission or the reverse.
In a release-enabled Local Agent build, KuCoin live actions require the separate default-off KuCoin setting and a selected account whose Spot, Futures USDT, or Futures USDC scope matches the active instrument. See Local Agent Live Trading API.
KuCoin includes automatic WebSocket recovery paths. Toggling the connection can be a troubleshooting step, but it is not the primary recovery model. Follow Connection Recovery when order state is uncertain.
Rithmic
Rithmic provides historical/live data, streaming depth, multiple broker-account identities, Market, Limit, Stop Market, and Stop Limit routing, and a native bracket path for supported presets.
Availability depends on the selected Rithmic system, credentials, entitlements, and plug-in/direct connection configuration. Always confirm the exact account identity before order entry.
Hyperliquid
Hyperliquid market data and LocalPaper are Current. Live wallet trading is Preview and unreleased for general use.
The wallet flow uses a dedicated locally generated agent key rather than the main wallet private key. It also requests a maximum builder-fee approval. Read Hyperliquid Wallet before connecting a wallet. If an enabled build will route Local Agent actions to that account, also follow Local Agent Live Trading API.
Binance
Binance is locked in the supported connection picker and is Unavailable / Coming Soon for clean public setup. Adapter code and legacy preconfigured state do not establish a certified market-data, LocalPaper, account, or order-routing workflow. Do not enter credentials or depend on Binance until its status is promoted in this matrix.
Order And Bracket Differences
Provider adapters do not report or modify orders identically.
Common active states include:
AcceptedAcceptedByRiskInitializedSubmittedTriggerPendingPartFilledWorking
Rithmic has a native bracket route for supported presets. Other routes can create protective orders after an entry fill. Confirm that every intended stop and target appears at the provider; an OCO preset in HyperionX is not proof that provider-side protection exists.
Order change support also varies. Some changes use a native modify operation, some require cancel-and-replace, and some are unavailable. Never assume a missing local order means the provider canceled it.
Credential Storage
Save Credentials is enabled by default for connection options. Credential-group values are encrypted on Windows using the current Windows user scope. Existing legacy plaintext credential values are migrated to protected storage when possible.
If credential saving is disabled, HyperionX clears saved credential values for that connection. Encryption at rest does not protect credentials from a compromised signed-in Windows account.
Never place API secrets, passwords, wallet session data, or agent keys in:
- Code Lab scripts
- Rion prompts or agent instructions
- logs or screenshots
- support messages
- source control
Connection Checklist
- Confirm the provider capability and status in the matrix.
- Select the intended environment and account.
- Grant only the provider permissions required for the workflow.
- Load instruments and historical data.
- Confirm live updates and depth where required.
- Confirm account, order, position, and execution state in a non-live environment.
- Test disconnect, reconnect, and unknown submission outcomes.
- Use controlled size only after provider-specific certification.
Troubleshooting
If a connection fails:
- Confirm the provider is supported for the required capability.
- Confirm credentials, environment, region, permissions, and entitlements.
- Check the application log without sharing secret values.
- Confirm historical data before diagnosing live updates.
- Confirm the instrument's tick size, lot size, multiplier, and provider identity.
- If an order may have been sent, stop new submissions and follow Connection Recovery.
Related pages: