Usage, exports, and alerts
Inspect calls by account, key, and model and manage usage alerts.
Inspect calls
Open usage, confirm the personal or team context, and filter by time, model, or key. Inspect request times, input/output usage, and USD charges using the fields available on the page.
If records are missing, check filters, the key's owning account, selected team, and refresh state. The public model catalog is not an account usage record.
Export and reconcile
Export an authorized range from the current page. Use consistent timezones and filters when comparing application diagnostics and console records, especially around day or month boundaries. For team summaries, select the month and member, model, or key grouping as shown.
Exports may contain business information and should be shared only with authorized recipients. Top-up or subscription payments and inference consumption are different types of records.
Configure alerts
In usage alerts, create the available balance, daily-spend, or member-cap rules and set their scope and threshold. Check enabled state and event history after saving.
Alerts are notifications, not substitutes for hard budgets or access restrictions. Event generation and email delivery are separate. If mail is missing, check the rule, address, and delivery state; missing mail does not prove there was no spending.
Investigate unexpected spending
Review keys and models in the affected period. Coding clients can issue helper requests, and conversation history is resent across turns. Disable suspicious keys and send sanitized details using the support template. See pricing for accounting concepts.