SDK reference

This page documents the official SDK’s full surface area: configuration, the bots.run loop, and every typed helper on the Trepa client. Skim the namespaces below when you know what you want to call; stay on Writing bots while you learn how the loop behaves. Most bots centre on trepa.bots.run; see Writing bots and Swarms. Everything after bots in this page helps when you step outside that loop (queries, claims, withdrawals, or raw HTTP). For HTTP fields and status codes, use the API Reference tab in the sidebar.

Construct the client

import { credentialsFromEnv, Trepa } from '@trepa/sdk'

const trepa = new Trepa({ credentials: credentialsFromEnv() })

With several bots, credentials is a list of { apiKey, privateKey } objects. See Swarms.

`new Trepa({ ... })`

The tables summarize constructor fields and the methods grouped under trepa.

Field	Purpose
`credentials`	One or more `{ apiKey, privateKey }` pairs.
`baseUrl`	Trepa API origin (defaults to production).
`solanaRpcUrl`	Solana HTTPS RPC (default `https://api.mainnet-beta.solana.com`).
`solanaRpcSubscriptionsUrl`	Solana WebSocket RPC (default `wss://api.mainnet-beta.solana.com`).
`balanceManager`	Targets for automatic funding when `TREPA_MASTER_PRIVATE_KEY` is set. See Master wallet.

Namespace	Purpose
`trepa.bots`	Prediction loop: `predict`, optional `updatePrediction`, hooks.
`trepa.auth`	Current user, refresh, logout.
`trepa.users`	Profiles, predictions, statistics, portfolios.
`trepa.pools`	List and fetch pools.
`trepa.streaks`	Bitcoin streak helpers and rewards.
`trepa.predictions`	Create and update predictions outside `bots.run`.
`trepa.rewards`	Claim pool payouts.
`trepa.withdrawals`	Send USDC externally.
`trepa.raw`	Typed HTTP with the same auth session.

auth

trepa.auth.me()
trepa.auth.refresh()
trepa.auth.logout()

refresh() is rarely needed; the SDK retries on 401 / 403.

users

trepa.users.get(userId, {})
trepa.users.predictions(userId, {})
trepa.users.statistics(userId)
trepa.users.portfolio(userId)
trepa.users.streakDetails(userId, streakId)

Use filters and includes where the API allows (see API Reference).

pools

trepa.pools.list({})
trepa.pools.get(poolId, {})

streaks

trepa.streaks.bitcoin()
trepa.streaks.poolDetails(streakId)
trepa.streaks.pools(streakId, { ... })
trepa.streaks.userDetails(streakId, {})
trepa.streaks.claimReward({ streakRewardId })

claimReward builds, signs, and submits on-chain; it needs privateKey on the matching credential.

predictions

trepa.predictions.create({ poolId, value, stake })
trepa.predictions.update({ predictionId, value })
trepa.predictions.updateStake({ predictionId, stake })

Each call is end-to-end (build, sign, submit).

rewards

After predictions settle you may claim rewards:

trepa.rewards.claim({ poolId, rewardId })

To load rewards beside predictions:

const me = await trepa.auth.me()
const predictions = await trepa.users.predictions(me.id, {
  includes: ['reward'],
})

withdrawals

trepa.withdrawals.create({ toAddress, amount, mintAddress })

Withdrawals are tightly capped. See Rate limits.

bots

Most automation uses this namespace rather than calling predictions by hand:

await trepa.bots.run({
  predict: (pool) => ({ value: 65_000, stake: pool.min_stake }),
})

predict may take a second argument, ctx, for slot context. Optional updatePrediction, hooks, and shutdown behaviour are in Writing bots. Multi-account context is in Swarms.

raw

When an endpoint is not wrapped yet, fall through to typed HTTP:

const { data } = await trepa.raw.GET('/pools/{id}', {
  params: { path: { id: poolId } },
})

If you rely on raw for something common, consider opening an issue so typed helpers can cover it.

Errors

Non-2xx responses throw TrepaError:

import { isTrepaError } from '@trepa/sdk'

try {
  await trepa.predictions.create({ poolId, value, stake })
} catch (err) {
  if (!isTrepaError(err)) throw err
  console.error(err.status, err.code, err.message, err.body)
}

Helpers

import { signTransaction } from '@trepa/sdk'

signTransaction signs a base64 Solana transaction with a base58 secret; resource methods use it internally. Without the npm package: Direct REST access, Rate limits.

Your first bot

Customize & scale

REST & limits

API reference

Construct the client

`new Trepa({ ... })`

auth

users

pools

streaks

predictions

rewards

withdrawals

bots

raw

Errors

Helpers

​Construct the client

​new Trepa({ ... })

​auth

​users

​pools

​streaks

​predictions

​rewards

​withdrawals

​bots

​raw

​Errors

​Helpers

Construct the client

`new Trepa({ ... })`

auth

users

pools

streaks

predictions

rewards

withdrawals

bots

raw

Errors

Helpers