{"name":"usage","stage":"ga","description":"Package usage is what your org ran and what it cost, broken down per account.","operations":[{"operationId":"post_usage","method":"POST","href":"/v1/usage","summary":"Ingests a batch of account-usage samples — what a developer's OWN AI accounts have consumed of their OWN plans, metered from each provider's own login — and appends them to the warehouse series."},{"operationId":"get_usage_analytics","method":"GET","href":"/v1/usage/analytics","summary":"Is the entitlement-GATED per-provider breakdown of the caller org's LLM usage — the paid lens over the same warehouse ledger GET /v1/usage/summary reads its totals from."},{"operationId":"get_usage_analytics_access","method":"GET","href":"/v1/usage/analytics/access","summary":"Echoes a plan's resolved analytics entitlement so a dashboard can configure itself against the LIVE catalog instead of hardcoding tier numbers."},{"operationId":"get_usage_samples","method":"GET","href":"/v1/usage/samples","summary":"Is the PER-PROVIDER view: one connected account's own consumption of its own plan — \"my plan is 47% through its 6h window, resets at 14:20\"."},{"operationId":"get_usage_summary","method":"GET","href":"/v1/usage/summary","summary":"Answers GET /v1/usage/summary: the caller's own usage footprint over one window — the categorized spend roll-up from the commerce ledger, the org's LLM usage totals from the warehouse (with what the prompt cache served and saved), the org's Kai decisions, and the caller's OWN linked provider accounts beside the org's Hanzo-routed usage."}],"_links":{"describedby":{"href":"/v1/openapi.json?capability=usage"},"self":{"href":"/v1/usage"},"up":{"href":"/v1"}}}