Spot & perpetual context
Approved market types expose account, symbol and position state in one workflow.
Features / Trading Desk
ReleasedTrading Desk with review before execution.
Manual spot and perpetual workflows are designed for paper trading and separately approved live paths, with permission and reconciliation boundaries kept visible.
AI assists. You decide.Capabilities
Order intent stays reviewable.
Market & limit orders
Order type, size, side and relevant settings remain explicit before submission.
Reduce & close
Position reduction and close paths preserve reduce-only intent where supported.
Cancel & synchronize
Single cancel, cancel-all and post-action refresh stay account-scoped.
How it works
From review to verified venue state.
The Desk separates what the user intends from what the connected venue ultimately confirms.
Review
Confirm account, market, order parameters and position context.
Resolve capability
Verify that the selected venue and environment allow the requested action.
Submit once
Use a permission-bound, idempotent mutation path.
Synchronize
Refresh orders, positions and account state after the venue response.
Safeguards
Critical mutations remain controlled.
A technical integration does not automatically authorize live writes, and a local response is not final account truth.
Permission
Account, symbol and action scope are checked server-side.
Protected credentials
Exchange credentials stay outside the browser execution path.
Degraded blocking
Missing critical live state can block submit, close and cancel actions.
Availability
Released with capability-specific boundaries.
The Trading Desk is released, while paper and live support still differ by venue, market type, account and environment.
Paper first
The first approval path uses no live capital.
Current or prepared paths
Hyperliquid, Binance, Bitget, MEXC, BingX and Paper Trading do not share identical capabilities.
No blanket enablement
A connected venue is not a promise that every write path is enabled.
Evaluation guide
Check the complete order path.
A trading interface should make intent, permission, venue response and final account state distinguishable at every step.
Before submission
Confirm the selected account, market, symbol, side, size, order type and position context before any paper or separately approved live request.
Capability match
Verify that the venue, environment and account support the requested market and action instead of inferring support from a successful connection.
Protected execution
Keep exchange credentials outside the browser path and route mutations through account-scoped, permission-bound services.
After submission
Compare orders, fills, positions and balances with venue state; an acknowledgement alone is not treated as final execution truth.
Connected workflow