Billing and Usage Monitoring
Applicable roles: Organization (top-level user), sub-user Last updated: 2026-07-14
The new console provides organizations with dedicated Dashboard and Usage Records pages, helping you answer "how much was spent this month, who spent it, on which models, and were there any anomalies" all in one place. This article explains what the dashboard shows, how to view usage by time and user dimensions, and considerations around metrics such as "today vs. cumulative."
1. Entry Points
| Entry | Path | Data Scope |
|---|---|---|
| Dashboard | Left navigation → Dashboard (/dashboard) |
Organization-level summary + sub-user distribution/ranking |
| Usage Records | Left navigation → Usage Records (/usage) |
Call details by time and user dimensions |
Data is strictly isolated by hierarchy: an organization sees only its own data, and a sub-user sees only their own usage after logging in. An organization can see the organization-level summary and the usage of each sub-user under it; sub-users cannot see other sub-users' data.
2. What the Dashboard Shows
After an organization logs in, the dashboard provides the following sections:
1. Balance Overview
Displays the current balance of the organization balance pool. All sub-user spending is deducted from here, and this balance is the sole source of funds. For low-balance alerts and overdraft behavior, see Balance Alerts and Overdraft.
2. Spending Trend
Displays the organization's spending trend over time, helping you gauge how quickly the balance is being consumed and anticipate when a top-up is needed.
3. Distribution by Model (Top)
Displays the spending/usage share of each model in your organization (ranked by Top), helping you understand which models your team primarily uses and where costs are concentrated.
4. Recent Usage
Displays call activity over a recent period, giving you a quick sense of current activity levels.
5. Quota Overview Card
Displays your organization's quota information on the platform, including the total quota cap, quota used, and so on. The quota cap is the spending limit the platform sets for your organization (i.e., the cumulative spending counter against the quota cap), which is a separate dimension from the balance -- the balance determines "how much money is left to use," while the quota cap determines "the maximum amount allowed to be spent."
After a sub-user logs in, their dashboard only shows their own usage overview, and there is a read-only "My Quota" bar at the top of the API Keys page showing their quota usage (format: "My Quota Used X / Y credits Remaining Z"). For the relationship between sub-user quotas and the organization balance, see Account System Overview.
Organization dashboard overview:

3. Viewing Usage Records by Time / User Dimension
The "Usage Records" page supports viewing call details by time range and user dimension:
| Dimension | Description |
|---|---|
| Time range | Filter call records by the selected time window |
| User dimension | Organizations can filter by sub-users under them to identify "who is spending" |
Each call detail in the usage records displays a routing source identifier, indicating which layer of routing resolution this call matched (Key-bound group / sub-user default / organization default / platform default / group identifier), making it easier to trace routing behavior.
Typical uses:
- Monthly cost allocation: Select the current month's time range and view each sub-user's spending by user dimension to allocate costs to departments.
- Identify high-consumption sub-users: Sort by spending to pinpoint the top-consuming sub-users and verify whether it is reasonable.
- Investigate abnormal calls: If you notice a sub-user's usage is abnormally high, combine it with the time distribution to determine whether there is a Key leak or an unauthorized script. If a Key is confirmed to be compromised, you can take action on the API Keys page.
After a sub-user is deleted, their historical usage is consolidated into the parent organization and is no longer retained separately under that sub-user dimension. Keep this in mind when performing historical reconciliation.
Usage records page:

4. The "Today" Metric and Time Filtering
4.1 Global Time Range Filter
The top of the dashboard provides a global time range filter (date range selection), allowing you to view statistics such as spending, model distribution, and user rankings for the selected time window. After switching the time range, the dashboard charts refresh to reflect that range's metrics.
4.2 "Today" vs. "Cumulative/Range" Metrics
Some dashboard statistics carry a "Today" badge, used to distinguish today's data from the selected time range/cumulative data. When reading the figures, first confirm whether a number is "today" or "the selected range" to avoid misreading a single day's spending as total spending, or vice versa.
Practical recommendation: For precise reconciliation, give priority to the results from the "Usage Records" details filtered by an explicit time range, and use the dashboard cards as a reference for trends and overview.
5. Data Notes
- Actual spending: The amount actually deducted from the organization balance, which serves as the basis for reconciliation.
- Data freshness: To optimize queries over large data volumes, some statistics may come from pre-aggregated snapshots and have a delay on the order of minutes; the interface labels the data update time.
- Details vs. summary: The dashboard shows "trends and distribution," while usage records show "line-by-line/item-by-item details." Both share the same data source but offer different perspectives.
6. FAQ
Q: Can an organization see sub-users' usage? A: Yes. On the dashboard, an organization can view the distribution and ranking of its sub-users, and in "Usage Records" it can filter details by sub-user dimension. Sub-users cannot see each other; a sub-user can only see their own.
Q: Are the numbers on the dashboard "today" or "total"? A: The top of the dashboard has a global time range filter for selecting a range; numbers with a "Today" badge use the current day's metric, while the rest follow the selected range. For precise reconciliation, rely on the results from "Usage Records" filtered by time range.
Q: Why is there a delay between today's data and what I actually feel? A: Some statistics use pre-aggregated snapshots to improve query performance, which may cause a delay on the order of minutes; this is normal.
Q: I deleted a sub-user—where did its previous usage go? A: It is consolidated into the parent organization and is no longer retained separately under that sub-user dimension.
Q: Does the dashboard data match the balance? A: The data source is the same, but the dashboard is an aggregated view (trends/distribution/ranking), while the balance reflects individual fund movements. For reconciliation, rely on the actual spending details.
