Skip to main content
Choose the data source that answers your question. A subscription balance, a conversation-cost chart, and a list of API requests describe different parts of workspace activity.
The public usage and API-request reports are not working activity reports. Their empty rows do not demonstrate zero usage, zero requests, or a complete audit history.

Review an interval

You need read access to the intended workspace and a clearly defined reporting period.
1

Confirm scope

Record the workspace, reporting dates, time zone, and any agent filters. Keep billing periods separate from custom analysis windows.
2

Read balances and operational metrics

Inspect credits_balance, credits_limit, and credits_used in the subscription response. Compare dashboard metrics with known conversation records before interpreting an empty chart.
3

Label the report's limits

Record missing data and the source of each figure. Do not derive invoices, pooled balances, or request-level accountability from placeholder reports.
For cost decisions, use cost optimization. For charges and payment terms, review the actual subscription and invoice workflow.
The contract includes grouping fields, but the current implementation does not calculate report rows.
Do not assume equivalence. Keep operational measurements and billing records identified separately.