# Usage and limits

> How KazoCode measures model usage, the 5-hour window and weekly limit, and where to see your spend by day, model and app on kazocode.app.

KazoCode models share one usage pool across every KazoCode app. The **Usage** page on [kazocode.app](https://kazocode.app/usage) shows how much of it you've used.

> [!NOTE]
> Limits apply only to KazoCode models. Models you use with your own API key or a local runtime never count toward them; those providers bill you directly.

## How usage is measured

Each request to a KazoCode model is priced from the tokens it uses at that model's rates, so a large model uses more of your limit than a small one, and long, multi-step agent work uses more than a short question. Cached input costs less than fresh input, and that saving counts in your favor.

## Two limits

1. **A 5-hour window.** The window opens with your first request and closes five hours later. The next request after that opens a new window.
2. **A weekly limit.** A rolling seven days of usage, so steady daily use fits comfortably.

The Overview page on kazocode.app shows the current window as a ring, and both limits as bars with when each one resets.

## The Usage page

| Section | Shows |
| --- | --- |
| **Spend** | Daily spend over the last 7 or 30 days |
| **Breakdown** | Spend by model and by app (desktop, CLI, mobile, chat), and a table of models with their tokens and cost |
| **Requests** | Every recent request with its time, model, app, tokens and cost |

Every number on the page is the number that counts toward your limits.

## In the app

For conversations that use your own keys, `/cost` estimates the current conversation and `/usage` reports tokens, cost, requests and tool calls per day and per model on your computer.
