The Usage & cost view

Usage & cost shows what your Coworkers, knowledge bases and system jobs have used, taken from the record of every model call. It is a view on the Governance page, selected with the Usage & cost button above the period control (the other view is Reviews). You need the admin or people_manager ability. Other people who select Usage & cost see "Viewing usage requires the admin or people manager role."

The numbers cover the whole company, not just the Coworkers you supervise.

Choose a period#

Under the Usage & cost and Reviews buttons, a period control offers three choices:

• This month: from the first of the current month to the first of next month.
• Last month: the previous calendar month.
• Custom: two date fields, From and To. The To date is included in full.

Months are calculated in your browser's time zone. In Custom, the page asks you to "Choose a start and end date (the end on or after the start)." until both dates are valid.

Totals#

Above the tables, five tiles summarize the period:

Tile	Meaning
Total cost	Spend in US dollars. See How cost is calculated.
Calls	Number of model calls.
Input tokens	Tokens sent to models.
Output tokens	Tokens returned by models.
Errors	Calls that failed.

If nothing was recorded, the page shows "No usage in this period". The tiles and tables appear as calls happen. If the page cannot load, it says "Usage couldn't be loaded. Try again in a moment."

Breakdown tables#

Each table has the columns Calls, Input tokens, Output tokens, Errors and Cost, sorted by cost with the highest first. A table with no rows says "No usage in this period."

Table	One row per	Notes
Coworkers	Coworker	Chat and conversation-compaction calls made for that Coworker.
Knowledge Bases	Knowledge base	Ingestion and search calls. A row named Search embedding collects search queries, which are not billed to one knowledge base. No Knowledge Base recorded collects ingestion calls that were not tied to one.
System jobs	Job name	Background work that no single Coworker or knowledge base owns, such as job description analysis and conversation compaction. Rows are named by the job's recorded name, for example jd-analysis. Knowledge base jobs are not listed here.
Teams	Team	Each call is attributed through its Coworker's team, or else its knowledge base's team. Calls with neither land in Unassigned.

A Coworker, knowledge base or team that has since been deleted still appears, with "· removed" after its name, so past spend stays visible.

Every call is counted once within a table. The tables are different views of the same spend, so do not add them together: a call appears under its Coworker and also under that Coworker's team.