Usage & Cost Admin API Cookbook

Why it matters

Finance sees the organization’s bill, not your features. Chargeback starts with the provider’s own record of usage and cost.

What to practise

With an Admin API key, query usage_report/messages in 1m, 1h or 1d buckets, grouped by model, service tier and workspace, and filtered by model and tier. Follow has_more and next_page through the pages. Query cost_report, which offers daily buckets only, grouped by workspace and description, and export both to CSV. Note that Priority Tier costs never appear in the cost report and that the API is built for historical analysis, not real-time monitoring.

How it fits

These reports are the organization half of 4.6.2’s ledger. They know models, tiers and workspaces, not your features, so feature attribution has to come from your own call records, as 4.6.1 describes. Because the reports are historical, compare them with the live signals that 4.6.3’s alerts need.