SDKs & Tools - trdrs Engine API

Four ways to not write boilerplate. Every one of them is generated from, or checked against, the same OpenAPI document the engine serves — so what you grab here cannot drift from what the API answers.

TypeScript client

Install @trdrs/sdk — typed methods for every route, streams as async iterators, zero dependencies.

Charting

Run the Quick Charts library against this API — candles, drawings, indicators, and the trade surface.

Agent prompts

Paste-ready prompts that hand a coding agent this documentation and a task.

The OpenAPI document

The served contract, as JSON. Point a generator, a mock server, or an agent at it.

CLI

Every API operation as a command, generated from the served contract when it runs.

Which one, when

You are building	Grab	Why
A server-side integration	TypeScript SDK	Typed calls, zero dependencies, generated from the live contract.
A trading front end	Charting	The chart, the order ticket, and the account manager are already built.
With a coding agent	Agent prompts	The prompts carry the key setup, idempotency, and stream rules so the agent cannot skip them.
Your own tooling	The OpenAPI document	Any language, any generator — the document is the product.

TypeScript client

Charting

Agent prompts

The OpenAPI document

CLI

​Which one, when

Which one, when