Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.trepa.io/llms.txt

Use this file to discover all available pages before exploring further.

Trepa’s HTTP API applies per-IP limits. When you exceed a bucket, the server answers with 429 Too Many Requests. Wait briefly, then retry with exponential backoff. The @trepa/sdk bot loop already spaces work sensibly; custom scripts should mimic that discipline.
AreaLimitWindow
Default (most read-only endpoints)120 requests1 minute
Auth (/auth/session, /auth/refresh, /auth/logout, /auth/login)15 requests per endpoint1 minute
Transaction create and submit routes (predictions, stake updates, claims)10 requests per endpoint1 minute
Withdrawals (/transactions/withdraw, /transactions/withdraw/submit)20 requests per endpoint24 hours
Withdrawal rows are a hard daily quota, not a per-minute burst limit. Other rows reset each minute. Production traffic that needs a higher ceiling should go through Trepa support with your use case and expected volume. For day-to-day integration work, keep the API Reference tab open beside this guide. When you step off the TypeScript SDK, Direct REST access stays the companion page for raw HTTP.
Last modified on May 2, 2026