Rate limits
The REST API enforces rate limits per key. The limit depends on the subscription tier ; above it, requests return 429 with a Retry-After header.
Response headers
X-RateLimit-Limit: <max requests per window>
X-RateLimit-Remaining: <remaining in current window>
X-RateLimit-Reset: <epoch seconds when window resets>
Retry-After: <seconds to wait, only on 429>Best practices
- Honor Retry-After and use exponential back-off on 429.
- Cache immutable responses (catalog, education).
- Prefer the /stream/scores endpoint for real-time updates.
Institutional disclaimer
Trinity Insights is an educational and analytical tool. Content does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114, nor a Financial Investment Advisor (CIF), nor a PSAN. See the full disclaimer.