Overview
TRON Charts is a multi-venue trading platform exposed as one API. The same credential reaches four things:
- Trading — compose, sign, and dispatch order intents across every wired venue, then read back positions, fills, and balances.
- Real-time state — depth, tape, marks, and account risk over WebSocket.
- A white-label DEX — a trading venue under your own brand, backed by the platform’s execution, market-data, and risk engine.
- An on-chain prop firm — a funded-trader program where custody stays at your multisig and the rules are committed on-chain.
Who each surface is for
Section titled “Who each surface is for”| You are | You want | Read |
|---|---|---|
| A trading application or bot | Orders, positions, market data | Quickstart → Orders & OMS |
| A broker or venue operator | Your own branded trading front end | Launch a DEX |
| A prop-firm operator | Challenges, deposits, payouts | Launch a prop firm |
| An agent builder | Tools instead of REST calls | MCP server |
The shape of the API
Section titled “The shape of the API”Everything public lives under two prefixes:
/api/v1/*— the versioned provider API. Bearer JWT (or a browser cookie session). This is the surface documented here and the one the SDK targets./ws/*— three WebSocket channels:/ws/market,/ws/risk,/ws/quotes.
Requests resolve to a tenant — the branded deployment you belong to — and every read and write is scoped to it. See Tenancy.
What the platform does not hold
Section titled “What the platform does not hold”The trust boundary is the API, not your wallet. The platform never takes
custody of a partner’s funds: a prop firm’s PropInstance contract is owned by
the multisig address you supply, deposits go straight to it, and payouts are
authorised by you. See Trust & custody model for the
full statement of what is and isn’t held.