---
title: 'Usage'
description: 'Read project usage and model consumption in the correct billing context.'
---

# Usage

Select your project and open **Usage**. Confirm the project and date range before comparing totals. The Current Billing Cycle selection is useful when investigating current service restrictions.



## Read the sections

| Section           | Purpose                                          |
| ----------------- | ------------------------------------------------ |
| Overview          | Overall usage context for the selected interval. |
| Spend by Model    | Compare model spending.                          |
| Requests by Model | Compare model request counts.                    |
| All Tokens        | Inspect token consumption.                       |
| API Requests      | Inspect API request usage.                       |
| DB Capacity       | Inspect database capacity consumption.           |
| Assets Storage    | Inspect asset storage consumption.               |

Read the units shown with each metric. A request count, token count, storage amount, and currency amount cannot be compared directly. Team-level views can have a different aggregation and access context from a project view.

## Investigate unexpected usage

Compare the interval with recent deployments, imports, requests, or automation runs. Use [Logs](/docs/dashboard/logs) for request-level diagnosis and [Run History](/docs/automations/runs) for automation outcomes. Repeated failing work may still consume resources.

Review **Settings → Spending** for project usage controls and team **Billing → AI Credits** for credit controls. Those settings are distinct. Use the current account UI for allocations and prices rather than assuming values from a screenshot.


---

[View full sitemap](/docs/sitemap.md)