> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/control-center/cost-control/credit-usage.md).

# Credit Usage

Review credit consumption, usage trends, and transaction history.

Review your account's credit consumption and transaction history. Open **Billing → Credit Usage**.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-3b7ad111fc4cf529cb3adad46b907b3c3258863c%2Fqore_control-center_control-centre-billing-credit-usage_rounded_shadow.png?alt=media" alt="The Credit Usage screen, showing available and used credits with a usage trend chart"><figcaption><p>Credit Usage, showing available and used credits and consumption trends.</p></figcaption></figure>

### Review credit usage

Narrow results by project and date range. The page shows **Available credits** and **Used credits** for the selected period. **Usage Trends** plots consumption over time.

**Resource Usage** breaks down spending across four tabs: **Apps**, **Agents**, **Models**, and **Features**. Each row lists a resource's **Name**, **Credits Used**, and **Last Used**.

Resource usage can lag live activity by up to one hour.

Select **Set usage limit** to open [Usage Limits](/control-center/cost-control/usage-limits.md). Select **View Ledger** to open your full credit history.

### Credit history

**View Ledger** opens the **Credit History** dialog. It lists every credit and debit transaction for your account.

| Column                 | What it shows                                                                  |
| ---------------------- | ------------------------------------------------------------------------------ |
| **Operation Type**     | **Debit** for credits spent or **Credit** for credits added                    |
| **Additional Details** | What the transaction was for, such as *Action Deduction* or *Credits Addition* |
| **Credit Change**      | The amount added or deducted                                                   |
| **Balance Credit**     | The running balance after the transaction                                      |
| **Timestamp**          | When the transaction occurred                                                  |

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-6a4429c7ec3f9600c01f7d161f340f09ddb94a73%2Fqore_control-center_control-centre-billing-credit-usage-limits-view-ledger-credit-history_rounded_shadow.png?alt=media" alt="The Credit History dialog, listing debit and credit transactions with running balance"><figcaption><p>The Credit History dialog, opened from **View Ledger**.</p></figcaption></figure>

### Related

{% content-ref url="/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/start-here/control-center.md)
{% endcontent-ref %}

{% content-ref url="/pages/4023fee41d519b1fbe13cbf03c9027c75b45de1a" %}
[Observe](/control-center/observe.md)
{% endcontent-ref %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/control-center/cost-control/credit-usage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.