Before you begin
- Sign in to the Admin UI with an organization-admin or server-admin account.
- For organization-scoped reports, select the organization you intend to review.
Choose the correct usage scope
| Role | Available scope at /usage | Primary views |
|---|---|---|
| Organization admin | Current organization | Overview, Users, Reports, Models, Providers |
| Server admin with an organization selected | Selected organization | Overview, Users, Reports, Models, Providers |
| Server admin in system view | All organizations | Overview, Models, Providers, Organizations |
- Role
- Organization admin
- Available scope at /usage
- Current organization
- Primary views
- Overview, Users, Reports, Models, Providers
- Role
- Server admin with an organization selected
- Available scope at /usage
- Selected organization
- Primary views
- Overview, Users, Reports, Models, Providers
- Role
- Server admin in system view
- Available scope at /usage
- All organizations
- Primary views
- Overview, Models, Providers, Organizations
- 1
Open Reports → Usage
Go to /usage. Server administrators should verify whether the page is in system view or organization view before interpreting totals.
- 2
Set the date range
Organization reporting windows use the selected organization's configured timezone. /usage waits for that timezone to resolve before enabling organization-scoped reporting; it does not silently substitute UTC.
- 3
Choose an entity view
Compare users, models, providers, daily activity, report totals, or quota-monitor rows without assuming that every tab uses the same aggregation.
Interpret cost and model identity carefully
- Current local-day and month-to-date cards use the organization's reporting day and month; a selected-window card uses the date range above it.
- An alias and its backing model are separate identities. Use the displayed alias and backing-model fields when tracing a request.
- Top slices may be approximate or clamped when the requested window exceeds the available ranking window. The UI and export include this context where applicable.
- Absence of a cost value does not mean the activity was free; pricing may be unavailable.
Export the report you are viewing
- 1
Set scope, range, and tab first
CSV export follows the active system or organization scope, selected date range, filters, and active tab.
- 2
Choose Export CSV
Wait for the export to finish before changing scope. The file includes identifiers and partial-cost flags needed for later reconciliation.
- 3
Retain the report context
Record the displayed timezone and whether rankings were approximate or clamped alongside the CSV.
Use the related operational views
| Route | Who can use it | Use it for |
|---|---|---|
| /ops | Server admin or an operator with local-diagnostics access | Current health and activity; this view intentionally omits cost |
| /metrics | Server admin | System and selected-organization metric series |
| /provider-errors | Organization admin or server admin | Recorded provider failures, request correlation, and CSV export |
| /catalog-health | Server admin or an operator with local-diagnostics access | Degraded or unknown provider/model catalog snapshots |
- Route
- /ops
- Who can use it
- Server admin or an operator with local-diagnostics access
- Use it for
- Current health and activity; this view intentionally omits cost
- Route
- /metrics
- Who can use it
- Server admin
- Use it for
- System and selected-organization metric series
- Route
- /provider-errors
- Who can use it
- Organization admin or server admin
- Use it for
- Recorded provider failures, request correlation, and CSV export
- Route
- /catalog-health
- Who can use it
- Server admin or an operator with local-diagnostics access
- Use it for
- Degraded or unknown provider/model catalog snapshots
Unlike /usage, some related operational views can continue with an explicitly labeled UTC fallback when an organization timezone is unavailable. Read the timezone notice on /provider-errors, /metrics, or /catalog-health before comparing timestamps.