Tria API Trading
Programmatic access to Hyperliquid and Decibel perpetual futures through Tria. One client, two venues, normalized order / fill / position shapes — with Tria builder-fee attribution wired in by default.
Three ways in
The same trading surface, three front doors. Pick the one that fits how you build.
- TypeScript SDK —
@tria-sdk/api-trading. A pure client library for deterministic bots, terminals, and services. Node 18+ and modern browsers. - MCP server —
@tria-sdk/api-trading-mcp. Put the SDK behind the Model Context Protocol so Claude, Cursor, or any agent trades in plain English — credentials never reach the model. - Python SDK —
tria-trade. Mirrors the TypeScript surface 1:1 (in progress).
Both venues always trade on real mainnet markets. There is no testnet target — the only environment knob is which Tria builder/treasury fees route to. Your agent and delegate keys are trade-only: they can place and cancel orders but cannot withdraw funds.
What you can do
Place, cancel, modify, and batch orders; attach TP/SL; close positions; read balances, margin, fills, and positions; pull markets, orderbooks, candles, and tickers; and stream fills, orders, positions, and account snapshots — all through one normalized interface across both venues.
Get started
Quickstart
Install @tria-sdk/api-trading and place your first order on Hyperliquid or Decibel in minutes.
Credentials
Mint an SDK environment from the Tria app and wire the keys into your config or .env.
Trading & orders
Place, cancel, modify, batch, attach TP/SL, and close positions across both venues.
MCP in Claude Desktop
Wire the MCP server into Claude Desktop and trade by talking to an agent — in five minutes.
Explore the API
TypeScript SDK
@tria-sdk/api-trading — one TriaClient for Hyperliquid and Decibel. Place, cancel, modify, stream fills and positions, all with builder-fee attribution.
MCP Server
@tria-sdk/api-trading-mcp — let Claude and other LLMs trade through the same SDK, with per-call approval and credentials the model never sees.
REST API reference
The HTTP surface behind the SDK — orders, positions, account, and market data, documented endpoint by endpoint.
Credentials
How to mint an SDK environment from the Tria app and where each key goes. Your keys stay on your machine.