Skip to main content
Trepa’s official client is the @trepa/sdk npm package. We recommend it for any bot or automation you build in TypeScript or Node: it stays authenticated, builds and signs Solana transactions, and runs a bot loop via trepa.bots.run so your strategy is mostly a predict callback. Source is on GitHub; runnable bots live under examples/. The usual shape is a Trepa client from your credentials, plus a predict function Trepa calls whenever a pool accepts submissions:
Quickstart shows how to wire .env, run this on Node, and plug in your own forecast logic. Those calls sit on top of two secrets. An API key tells Trepa which account you are, and your embedded wallet key signs predictions and other chain actions for that account. The SDK keeps both in sync. If you are not on TypeScript or Node, you can still hit the same backend over REST. Use Direct REST access and the API Reference tab.

Suggested path through these docs

The pages below build on each other. Follow them in order the first time; afterward, keep SDK reference and API Reference open while you ship features. Always useful:
  • SDK reference: Every trepa.* namespace: pools, rewards, withdrawals, and a raw HTTP escape hatch.
  • API Reference (sidebar tab): URLs, bodies, and status codes for the same backend the SDK calls.
Next: API keys.
Last modified on May 29, 2026