Skip to main content
AI Usage sits in the AgentHub sidebar right after Model Manager. It shows what your organization spends on AI, who spends it, on which models and features, and how much personal or sensitive data was stripped out of prompts before they reached a provider.
AgentHub has no Playground in its sidebar. AI Usage takes that slot. The prompt-comparison Playground only exists on CorePillar’s demo build.

Who sees what

The page decides your view from your role, on the server. Nothing in the URL can widen it. The organization view opens by default. Just me switches to your own numbers and adds ?scope=personal to the URL; Organization removes it. Both views start loading when the page opens, so switching is instant once the second one has arrived.
The /playground address on AgentHub also renders the organization dashboard, gated on the manage_org_settings permission (Owner and Admin by default). Anyone without it sees “Not available on your account — Org-wide AI usage and cost is visible to workspace owners and admins. Your own usage is on the AI Usage page.” Use the AI Usage sidebar item; the result is the same data. See Roles and permissions.

Header and filters

The title is AI Usage & Cost with your organization’s name underneath, or My AI usage / “Your activity only” in the personal view. Each filter panel has Select all and Clear, closes on Escape or a click outside, and writes its choice to the URL (?users= and ?projects= as comma-separated IDs), so a filtered view can be bookmarked or shared with another admin. Switching to Just me drops the user and project filters. Days are UTC calendar days. The window ends now and reaches back 7, 30 or 90 days.

Where the numbers come from

Every figure is a sum over four sources. Each source is attributed to the person who triggered it. Chat data comes from ModelHub, which shares your organization’s data with AgentHub. If nobody in the organization uses ModelHub, the chat-only sections below (PII, routing, latency, right-sizing) stay empty.

KPI tiles

The change reads “flat” when it rounds to 0%, and ”—” when the previous window had nothing to compare against.

Spend over time

An area chart of daily spend across all sources, with a dashed Requests (relative) line. The requests line has no axis of its own; it is scaled to the chart so you can compare its shape with spend. Hover a day to see the date, its spend and its request count. “No data yet” when the window is empty.

Spend by source

A table with one row per source, plus a stacked daily bar chart of cost by source. Only sources with spend get a series in the chart.

Cost by user (organization view)

Horizontal bars for the top 10 people by spend. Each bar shows the person’s name, their spend, and their share of total spend. People who have since left the organization still appear by name. Someone whose profile can’t be found shows as “Unknown user”. This is cost per person across every source: their chat turns, the Cost Calculator runs they started, and any evaluations they ran.

Tokens in / out and Activity (personal view)

In Just me and in an Editor’s view, the Cost by user card is replaced by two cards:
  • Tokens in / out: stacked daily bars of input and output tokens. Hover a day for “date: N in · N out”. “No token activity yet” when empty.
  • Activity: a calendar heatmap of requests per day, Monday-first, with a Less … More legend. Hover a cell for the date, request count and cost. “No activity in this window yet” when empty.

Model mix

A donut of spend by model with Total spend in the centre, and a table:

PII leakage

ModelHub strips personal and sensitive data (names, email addresses, card numbers, API keys and so on) out of prompts before they reach a provider. This card summarizes what was stripped. It covers chat only.
  • Events over time: daily count of identifiers stripped. A “N turns blocked” badge appears when some turns were held back entirely because of what they contained.
  • By severity: a single bar split into Critical, High, Medium and Low, with counts.
  • By type: the top 8 identifier types, coloured by severity.
“No PII detected” appears in each part when there is nothing to show.

Stripped identifiers (organization view only)

Under the PII card, admins see the itemized log: every identifier type stripped from every turn, newest first. “Visible to workspace administrators only. Credentials and government identifiers are stored partially masked — enough to identify which one leaked, not enough to use.” A summary strip shows the total (“N stripped”), a count per severity, and “N turns held” when any turns were blocked. Two filters narrow the table: All severities and All types. The log holds the 300 most recent entries in the window. It is an audit view, not an export. Empty states: “Nothing has been stripped yet — prompts so far contained no detected identifiers.” and, when a filter excludes everything, “No matches for this filter.”
The Stripped value column shows the actual personal data your people typed. Only Owners, Admins and super admins can see it. The personal view never loads it: when you switch to Just me, the log and the member list are removed before the data reaches your browser.

Routing & savings

Chat-only figures from ModelHub’s automatic model routing. The card header carries three pills when there is data: Right sized, Overpowered and Underpowered, each with a count and share of chat turns.

Demo data

If CorePillar set up a demo for your organization, it may have loaded a sample usage history: roughly 60 days of chat turns from synthetic coworkers, plus a share attributed to the person the demo was prepared for. The synthetic coworkers are added to the organization as Viewers and their accounts are blocked from signing in. Every seeded row is tagged, so CorePillar can remove the whole set on request. Real usage is never mixed into or altered by it. If you see unfamiliar names in Cost by user in a new organization, ask your CorePillar contact whether a demo dataset was loaded.

How this differs from ModelHub’s Usage page

ModelHub’s Usage page is the same screen, built on the same calculation: Because personal and organization views run the same aggregation, an employee and their admin always see identical numbers for the employee.

ModelHub Usage

The employee-facing view of the same data.

Cost Calculator

The source of most non-chat spend in AgentHub.

Roles and permissions

Which roles see the organization view.

Model Manager

Where model prices come from.