> For the complete documentation index, see [llms.txt](https://docs.avis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avis.net/guide/console/dashboard.md).

# Dashboard

The **Dashboard** gives you a quick overview of how much you're spending, on what, and through which keys. Open it from **Dashboard** in the Console sidebar.

The Dashboard refreshes automatically every 30 minutes.

***

## Choose a time range

Use the buttons at the top right to switch between **24h**, **7d**, **30d**, **90d**, and **1y**. Use the time zone selector (for example **GMT+7**) so dates line up with your local day.

***

## Summary cards

| Card                    | What it shows                                                                               |
| ----------------------- | ------------------------------------------------------------------------------------------- |
| **Total cost**          | Credits spent in the selected period, platform fee included                                 |
| **Total requests**      | Number of requests made                                                                     |
| **Total tokens**        | Tokens processed across text and token-billed models                                        |
| **Top API Key by Cost** | The key that spent the most, with the beginning and end of its value so you can identify it |
| **Top Model by Cost**   | The model you spent the most on                                                             |
| **Usage type**          | How your spending splits between **Direct API** calls and the **AVIS Playground**           |

**Tip:** If one key suddenly shows up as your top spender, check that it hasn't leaked. Lower its spend limits or revoke it on the **API Key** page.

***

## Cost over time

The chart shows your daily spending over the selected period.

* Use **Cost over time** to switch between viewing cost in credits and other metrics.
* Use **By Model** to break the bars down by model, and **All models** to focus on a single one.
* Use the modality tabs (**All modality**, **Chat**, **Image**, **Video**, **Audio**, **Embedding**) to look at one type of usage at a time.
* Click the expand icon to open the chart full screen.

Below the chart, a table lists each model with its modality and the **minimum**, **maximum**, and **average** cost per request, plus its total spend and share of the total.

***

## What's Next

* Need request-level detail for a specific key or date range? Use [Usage Query](https://docs.avis.net/guide/console/usage-query.md).
* Want to cap spending? Set spend limits on each key, see [How to get API Key](https://docs.avis.net/guide/get-started/avis-api-key.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avis.net/guide/console/dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
