Skip to content
CortexDocs

Inspect usage and spend

Filter captured Gateway usage by time, model, provider, team or member, then inspect estimated spend and pricing coverage.

Find captured-spend contributors within one reporting range and filtered population.

Before you begin

Required

  • Cortex Atlas

    Atlas must be enabled for the intended organization.

  • Account visibility

    Use an account that can view the intended organization. Sample views have fixed data and disabled live filters.

Read each member's requests, spend and seven-day activity on the Members pageOpen in Cortex
  • Estimated spend prices captured activity over the selected reporting window. Unknown or unpriced cost is not zero, and it is not an admission balance. Reference prices captured activity, not the complete bill or an authoritative admission balance.
  • Missing usage or rates can leave activity unpriced. Unknown cost is not zero.

Read usage by person and team

  1. Open Access & limits → Members. Each row is one person. Requests 30D counts what they sent, Spend 30D shows what it cost, and Activity 7D draws the last seven days.
  2. Read Activity 7D. The line is green when usage is rising and red when it is falling.
  3. Open Access & limits → Teams. The tiles summarize the organization. The table splits the total by team, with each team's spend next to its budget.
  • To see which key a cost came from, open API Keys. Each key shows Spend 30D next to its status.

This 0:49 recording walks through the Members and Teams views with example data.

Guided tutorial0:49

Read usage and spendUse the chapter list to move through the walkthrough.

Narrow the population

  1. Open Usage and select 7D, 30D or 90D.
  2. Open Filters. Under Group results by, choose Model, Provider, Team or Member.
  3. Choose a Time bucket and any Team, Member, Model or Provider filters. Search for the intended subjects.
  4. Select Apply filters. Confirm the selected chips, reporting window, grouping and bucket beside the chart.
Filter members by team, type, status and reporting windowOpen in Cortex

Grouping changes the breakdown; filters change the included activity. Keep the same selection when comparing results. Check Teams and hierarchy when memberships overlap.

Read the breakdown

  • Compare Estimated spend, Captured activities, Input tokens and Output tokens on the same row.
  • Expand model families under Model grouping. Use Previous and Next for additional rows in other groupings.
  • To investigate a contributor, filter to it while retaining the reporting range, then regroup if needed.
  • Use AI spend for deeper inspection.
  • A grouped row summarizes activity. Open an individual exchange only when the view provides a link.

Check the comparison

  • Match the range, subject filters, visibility, currency and pricing coverage.
  • A chart showing the first 500 grouped entries is partial. Neither it nor one table page represents the full population.
  • Unknown means unresolved model identity, not a provider. Keep unpriced activity visible; $0.00 alone does not establish free usage.

Understand estimated spend

  • For provider reconciliation, use rates effective during the usage period. The current model catalog can differ.
  • Check organization pricing, input, output and cache treatment, usage coverage, currency, time window, adjustments, retries and incomplete requests.
  • A contracted rate does not guarantee an invoice match. Use Manage budgets to configure admission controls separately.

Troubleshooting

SymptomNext action
No matching rowsCheck range and filters; only matching captured activity is returned.
Usage fails to loadRetry the read before interpreting the totals.
Filters disabledCheck whether this is a fixed sample view.
Unresolved or unpriced contributorCheck identity, captured tokens and pricing coverage.
Totals differAlign population, visibility, window and pricing coverage.