TRON Charts
One API to trade, stream live market state, launch a white-label DEX, or run an on-chain funded-trader program.
Start from a task
Section titled “Start from a task”Each recipe is one concrete job — the calls, in order, with code you can paste. Three to five steps, no preamble. See all 15 recipes
Place your first orderCompose an order intent and watch it reach the book.
Attach a take-profit and stop-lossTwo reduce-only legs, OCO-linked to an open position.
Stream account and position updatesOpen /ws/risk and subscribe to the topics you care about.
Create a prop firm challenge templateThe product a trader buys — size, fee, split, and the rules that judge it.
Pick your path
Section titled “Pick your path”TradePlace, modify, and cancel orders across every wired venue from one order surface.
StreamDepth, tape, marks, and account risk over three WebSocket channels.
Launch a DEXA white-label venue under your brand, backed by our execution, market-data, and risk engine.
Launch a prop firmAn on-chain funded-trader program — templates, deposits, payouts. Custody stays at your multisig.
Three ways to integrate
Section titled “Three ways to integrate”Three surfaces, one platform. REST reaches everything; the SDK and MCP server cover most of it.
| Surface | What it is | Start here |
|---|---|---|
| REST | https://api.troncharts.xyz/api/v1/* |
REST reference |
| TypeScript SDK | npm install @tronchartsxyz/api-client |
TypeScript SDK |
| MCP server | npx @tronchartsxyz/mcp-server — agent-native tools and prompts |
Build with an AI agent |
Built to be read by an agent
Section titled “Built to be read by an agent”Every page here is plain Markdown behind the scenes, and two machine-readable
index files sit at the API root: /llms.txt
maps the corpus, /llms-full.txt
concatenates it. Point Claude at either, or connect the
MCP server and let it call the API directly.