Usage & rate limits
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.
- Person and company reports (
/dossierand/entity/dossier) are cached privately for each account. Repeating the same request from the same account, with any of its keys, replays the cached report instantly and does not consume usage; only a fresh build, includingrefresh: true, is charged. Reports are not shared between accounts, so each account builds and pays for its own./vinreports use a shared vehicle cache, so a VIN that is already cached replays for free. - When included usage and extra credits are both exhausted, metered requests return
402 usage_exhausted. - Default per-key limits are
60/minfor search,30/minfor dossier, and60/minfor chat, plus an IP abuse ceiling. - Production keys can also carry an optional monthly compatibility budget. Budgeted keys return
402 api_key_budget_exceededbefore spending more usage.
Responses include
percentageCharged, remainingPercent, resetAt, and source. Deprecated credit fields and headers remain for the v1 compatibility release.