Understand usage and quotas
Distinguish tokens, calculated cost, cumulative quotas, and request frequency.
What the numbers mean
- Token usage
- A unit of model consumption. Check the applicable recording rules for input and output.
- Calculated cost
- An amount calculated from usage and configured prices; it is not a payment invoice or financial settlement.
- Cumulative quota
- A configured usage boundary for a defined time range or period.
- Request frequency
- Management of request counts or rates over a period of time.
Compare records in the same scope
Align the organization, person, key, model, and time range before comparing aggregate usage with individual requests. Numbers with different scopes or accounting rules are not directly comparable.
Review organization, key, and model rankings
Daily organization usage in Usage & Billing uses UTC+8 dates. Switch the Top 20 between organizations, keys, and models. Rankings aggregate total tokens in the current filter independently of table pagination; organization administrators see only their organization. Model ranking combines the same model across keys and channels.
Key rankings show the first five characters of the current organization after the key name; hover for the full name. Deleted keys use the organization from their latest usage record; an organization filter shows the filtered organization. Each key has one aggregate entry within the filter. Percentages use all matching usage, including records outside the Top 20.
Understand the conditions for limits
Verify quota units, periods, behavior at the limit, and accounting under concurrent requests against the relevant release documentation and test results. A configured quota alone does not prove that overspending is impossible.
Match capabilities and procedures to your deployment version. Read the documentation scope