Skip to content
Developers
Getting started

Usage & rate limits

Understand account billing, caching, and rate-limit headers.

API usage draws on the same weekly general-usage allowance as the app. Each request settles from the model tokens and paid tools it actually uses. Lighter models and cached results stretch the allowance further.

  • Included usage is spent first, then non-expiring extra credits automatically. Extra credits do not unlock capabilities that are unavailable on the account's plan.
  • /dossier results are cached and shared. A cache hit returns instantly and does not consume usage; only a fresh build is charged.
  • When included usage and extra credits are both exhausted, metered requests return 402 usage_exhausted.
  • Default per-key limits are 60/min for search, 30/min for dossier, and 60/min for chat, plus an IP abuse ceiling.
  • Production keys can also carry an optional monthly compatibility budget. Budgeted keys return 402 api_key_budget_exceeded before spending more usage.

Responses include percentageCharged, remainingPercent, resetAt, and source. Deprecated credit fields and headers remain for the v1 compatibility release.