Skip to content

Rate limits & credits

Base URL: https://api.trinityinsights.io. The paths below are absolute on this host and already carry the /api/v1 prefix.

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.

Throttling signals

HTTP/1.1 429 Too Many Requests
Retry-After: 60          # limite de débit par clé
Retry-After: 86400       # quota anonyme journalier épuisé

Exceeding a limit shows as HTTP 429 with Retry-After; the body carries detail: Rate limit exceeded (per key) or Daily quota exceeded (anonymous quota). The API does not return X-RateLimit-* headers.

Credits & usage

Trinity Data access is metered in credits: 1 credit = 1 REST request OR 1 MCP tool call. Each plan includes a monthly credit allowance; per-plan allowances are listed on the pricing page.

  • The monthly allowance resets each billing cycle.
  • Paying subscribers can buy extra credit packs (valid 12 months), consumed only after the monthly allowance.
  • When the allowance and packs are exhausted, calls are paused until the next monthly reset or a new pack ; there is no automatic overage billing.
  • Track your balance in real time in the developer console.

Credits (call volume) and rate limits (req/min) are two distinct mechanisms: the rate limit caps the instantaneous pace, credits cap the monthly volume.

Best practices

  • Honor Retry-After and use exponential back-off on 429.
  • Cache immutable responses (catalog, education).
  • Prefer the /api/v1/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.