Skip to main content

Get the current account's billing standing

GET 
/v1/users/me/billing

The plan the account is on, how long its projects may keep content, how much indexed storage it is holding, and the credit it has left — the figures the platform already enforces against, readable by the account they are enforced against.

A managed-model generation is refused with 402 insufficient_credit while credit_balance_usd is negative, and a feature or a resource count outside the plan is refused with 403, as is a retention window wider than retention_days or an ingest past storage_limit_gb. Every refusal names what is missing; this is where the numbers behind them are read.

Every figure here is a local read, which is what keeps this route cheap enough to poll — unlike GET /v1/users/me/usage, which asks the meter once per project.

Answers for the caller's own account only, and always the account the credential resolves to — an API key answers for the user that minted it. The plan gating a project is that project's billing owner's, so a member of someone else's project reads their own rung here, not that project's.

Responses​

The account's plan and credit standing.