Skip to content

Authentication

The Trinity Insights API authenticates via an API key sent as an HTTP header. A key belongs to an account and a subscription tier ; every non-public endpoint requires the header.

One key, REST + MCP

Your Trinity Data key (tr_mcp_ prefix), created in the developer console, authenticates BOTH the REST API (this page) and the MCP server. Not two keys : one. For REST, send it as the X-API-Key or Authorization: Bearer header (both work). For MCP, configure it as the Bearer token.

HTTP header

X-API-Key: $TRINITY_API_KEY

Or, strictly equivalently, as a Bearer header (identical to the MCP server) :

Authorization: Bearer $TRINITY_API_KEY

The key prefix identifies its environment. Treat the key as a secret : it is equivalent to a password.

Key management

  • Created from the developer console (a key is revealed once).
  • Rotation at any time - the new key is active immediately, the old one revocable from the interface.
  • Immediate revocation : calls using the revoked key return 401.

Subscription tiers

Each key inherits the tier of its account. Capabilities, rate limits and accessible endpoints differ per tier. See the pricing grid.

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.