> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moxus.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage

> Review usage totals, trend charts, API activity, and account activity.

Usage is the page in the platform sidebar for monitoring your own account activity. Use it to review API call trends and recent records. For top-ups and balance history, use [Billing](/en/platform/billing).

## Page overview

The top of the page shows four metrics for the selected time range:

| Metric       | Meaning                                                  |
| ------------ | -------------------------------------------------------- |
| Total usage  | Balance consumed by API calls in the selected range      |
| Requests     | Number of API requests in the selected range             |
| Total tokens | Input tokens plus output tokens                          |
| API keys     | Number of keys that produced calls in the selected 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:

| Control                     | What it changes                                           |
| --------------------------- | --------------------------------------------------------- |
| Day / Week / Month / Custom | Recent 1 day, 7 days, 30 days, or a custom number of days |
| Hour / Minute               | Chart time granularity                                    |
| API Key / Model             | Whether charts group data by API key or by model          |

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.

<Tip>
  To find where cost came from, group by Model first, then switch to API Key to identify which key produced the calls.
</Tip>

## Recent activity

The Recent activity section has two views:

| View  | Contents                                                                                                     |
| ----- | ------------------------------------------------------------------------------------------------------------ |
| API   | API call records with time, API key, model, input tokens, output tokens, cache usage, total tokens, and cost |
| Other | Account activity such as recharge, management, system records, errors, refunds, or login records             |

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:

| Label  | Meaning                                                                                             |
| ------ | --------------------------------------------------------------------------------------------------- |
| Cache↓ | Tokens read from cache, which means cache was hit for this request                                  |
| Cache↑ | Tokens written to cache, sometimes split by 5-minute or 1-hour cache windows depending on the model |

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.

The downloaded file includes time, API key, model, input tokens, output tokens, cache tokens, total tokens, and cost. Use it for local records or team reconciliation.

## Troubleshooting paths

<AccordionGroup>
  <Accordion title="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](/en/platform/billing).
  </Accordion>

  <Accordion title="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](/en/platform/account-and-keys).
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## Next steps

* [Billing](/en/platform/billing)
* [API keys](/en/platform/account-and-keys)
* [Models and pricing](/en/overview/models-and-pricing)