# Usage Tab

The Usage tab functions to display information related to LLM service usage. In the Usage Analytics section, users can view the total cost incurred (Total Spent) as well as the number of remaining coins (Remaining Coins). This feature also provides time-range options such as 2 days, 7 days, 30 days, or custom ranges to monitor usage in more detail.

The Spending Trends section displays a spending trend chart based on time. This chart shows changes in usage costs within the selected period. If no activity has occurred, the chart will appear empty.

Next, in API Key Usage, users can see detailed API usage based on the number of tokens consumed and the costs generated by each API key. Meanwhile, Model Usage provides information about the LLM models used, including the number of tokens and associated costs. If no usage has occurred, both sections will display that usage data is not yet available.

<figure><img src="/files/f1jnWpIeos7tXodKDVfh" alt=""><figcaption></figcaption></figure>

## Date Range Filter

<figure><img src="/files/VnOe1T1Eea2CC4XK9s56" alt=""><figcaption></figcaption></figure>

In the highlighted section, there are several buttons: 2 Days, 7 Days, 30 Days, and Custom. These buttons function as time-range filters to determine the usage period displayed on the Spending Trends chart.

When the user selects one of these time ranges, the system will display the spending data and LLM usage activities according to the selected period. This allows users to monitor usage trends more accurately and based on their needs.

In addition to the quick options such as 2 Days, 7 Days, and 30 Days, users can also use the Custom option to manually set a specific tim e period.

On the Usage tab page, click **Custom** → **select the desired dates** → **click select button**

{% hint style="success" %}
**Note:**\
The **Custom Date** filter displays usage data in a detailed format, which limits the selectable time range.\
To view more data and more complete charts, it is recommended to select a period of **more than 2 days** using the **7 Days** or **30 Days** filter.
{% endhint %}

<figure><img src="/files/jncaO4gNACKyZmqs92rx" alt=""><figcaption></figcaption></figure>

## Total Coin Spend

<figure><img src="/files/9SwT4wt7OHpeqqaWNTJ8" alt=""><figcaption></figcaption></figure>

a. The **Total Spent** section displays the total cost or coins that have been used for the Deka LLM service. This information is presented in a blue card, with the usage value clearly shown in the center. In the example above, the value Rp0 indicates that no coins have been used. This section helps users understand how much has been spent during the selected usage period through the time-range filter feature.

b. **The Remaining** Coins section shows the number of coins still available for use in the Deka LLM service. This value is displayed in a green card, making it easy for users to quickly identify their remaining balance.

## Spending Trends

The Spending Trends section displays a chart that shows the progression or pattern of coin spending based on the selected time period. This chart helps users understand how many coins were used from day to day or within a specific time range.

In the display above, the chart appears empty because no coin usage activity has been recorded. If usage data is available, the chart will show lines or bars representing the amount of spending at each point in time.

<figure><img src="/files/AEtloJUJHYBga0aEF3Vg" alt=""><figcaption></figcaption></figure>

When the user **hovers over a data point** on the **Spending Trends** chart, the system displays a **tooltip** containing the **date** and the **total usage cost (Spent)** for that specific date.

This information helps users understand **daily usage details** based on a specific time period.

<figure><img src="/files/EeX9udjTTzHKWiXRunGo" alt=""><figcaption></figcaption></figure>

## API Keys Usage

The API Key Usage section displays a summary of API key usage in terms of cost (Spend) and the number of tokens (Tokens) consumed. This information helps users monitor the level of API call activity and the costs incurred from that usage.

<figure><img src="/files/qvfjnNNaMudX4vzCGsHK" alt=""><figcaption></figcaption></figure>

In the API Key Usage section, two display options are available:&#x20;

1. **Spend:**

The Spend option displays the total cost generated from the use of each API key, allowing users to monitor the expenses incurred from every API call.

To view spending data, open **API Key Usage**, then select the **Spend** tab.

<figure><img src="/files/JqgpQSOArxe6bemZzhzi" alt=""><figcaption></figcaption></figure>

2. **Tokens:**

The Tokens option displays the number of tokens consumed, enabling users to see the volume of API usage based on the model processing activity.

To view token usage data, open **API Key Usage**, then select the **Tokens** tab.

<figure><img src="/files/Vq8sQQeicmllQhwaBX33" alt=""><figcaption></figcaption></figure>

## Models Usage

Model Usage displays a summary of the usage of models created in Deka LLM. This section helps users monitor the activity of each model specifically, rather than by API key, making it easier to identify which models are used most frequently and how they contribute to costs and token consumption.

<figure><img src="/files/TJLRsJz2gl4DB4YlS8Pv" alt=""><figcaption></figcaption></figure>

In the Model Usage section, two display options are available:&#x20;

1. **Spend:**

The Spend option shows the total cost generated from the usage of each model, allowing users to see the amount of expenditure attributed to each model.

To view token usage data, open **Model Usage**, then select the **Tokens** tab.

<figure><img src="/files/QaEQzEqrAbBg2oYVwe62" alt=""><figcaption></figcaption></figure>

2. **Tokens:**

The Tokens option shows the number of tokens consumed by each model, enabling users to monitor the volume of processing performed by the model during its usage.

To view spending data, open **Model Usage**, then select the **Spend** tab.

<figure><img src="/files/mg8dAuo55vRhDCFDC3LW" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/guidance-for-individual/deka-llm/detail-deka-llm/usage-tab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
