Page overview
The top of the page shows four metrics for the selected time range:
These metrics count API call records. Requests sent from the web Conversation page use an internal virtual key and may appear with a key label such as
playground-key.
Time range and charts
Use the controls above the charts to change the range and grouping:
The page includes four charts:
- Total usage: balance consumption over time.
- Call trend: request count over time.
- Call count distribution: share of calls by key or model.
- Call count ranking: keys or models with the most calls.
Recent activity
The Recent activity section has two views:
Use API records for model usage and cost checks. Use Other records for account-level activity.
Cache hits
When a model request uses cache features, API records show cache-related token data in the Tokens column:
Open a record’s detail view to see the full token breakdown, including input, output, cache read, and cache write tokens. Not every model produces cache data; records without cache usage do not show cache rows.
View more and download
Click View more to open the activity history dialog. API activity history supports:- Selecting a start date and end date.
- Filtering records by API key.
- Paging through more records.
- Downloading API records for the selected filters as a text file. To download records for one API key, filter by that key first, then download.
Troubleshooting paths
Balance decreased and you need to find why
Balance decreased and you need to find why
Select the relevant time range on this page, group by Model to identify where usage came from, then group by API Key to find which key produced the calls. For top-up or balance movement history, check Billing.
An API key may be calling unexpectedly
An API key may be calling unexpectedly
Group charts by API Key and review that key’s call count and usage trend. If you see unfamiliar times or request spikes, delete or recreate the key in API keys.
You need to export call records
You need to export call records
Open View more in Recent activity, stay in the API view, select a date range, and click Download. To export records for one API key, filter by that key before downloading. The text export contains API activity only, not recharge, login, or other account activity.
How do I check whether cache was hit?
How do I check whether cache was hit?
Review the Tokens column in API records. Cache↓ means the request read from cache; Cache↑ means the request wrote to cache. Open the record details for the full breakdown of cache read, cache write, input, and output tokens.
You cannot see the full failure reason
You cannot see the full failure reason
The Usage page focuses on account-level statistics and activity summaries. For detailed troubleshooting, use the client error response together with request time, model name, and API key.