> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baseten.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Check your Grid usage

> See your Grid spend for the month against your limit, understand what happens at the limit, and manage your Grid API keys.

`baseten grid user-settings describe` shows what you've spent through Grid this month against your effective limit in a team. Grid attributes that spend to the Grid API keys you create, which you manage from the same CLI.

Before you begin, [install the Baseten CLI](https://docs.baseten.co/reference/cli/baseten/overview.md#install) and [sign in](https://docs.baseten.co/reference/cli/baseten/auth.md#login) to your organization.

## See your spend this month

Replace `<team>` with the team's name or ID, then run the following command for each team whose spend you want to check:

```sh theme={"system"}
baseten grid user-settings describe --team "<team>"
```

The result shows your spend for the current UTC month, your standing and current-month limits, your effective limit, and whether a member or team limit has blocked you. To break down usage by day or model, use `baseten grid route usage`:

```sh theme={"system"}
baseten grid route usage --team "<team>" --since 7d
```

Without a date range, route usage covers the previous UTC day through today, grouped by model. The terminal output is a table of daily token counts and estimated costs, followed by totals.

* Model API costs use your organization's prices and include tool calls.
* Anthropic, OpenAI, and xAI costs estimate what those providers charge. They aren't Baseten charges.

Usage excludes Vertex AI and OpenAI-compatible connections.

A cost of `-` means some usage couldn't be priced; it doesn't mean the usage was free.

Usage can lag by up to 15 minutes. To stream machine-readable usage, run the following command:

```sh theme={"system"}
baseten grid route usage --team "<team>" --since 7d --output jsonl
```

If you're signed in with a team or workspace API key and can't retrieve your own usage, sign in as yourself:

```sh theme={"system"}
baseten auth login
```

For more information, see [`baseten grid user-settings describe`](https://docs.baseten.co/reference/cli/baseten/grid#user-settings), [`baseten grid route usage`](https://docs.baseten.co/reference/cli/baseten/grid#route), and [Compare usage views](https://docs.baseten.co/grid/manage.md#compare-usage-views).

## When you reach a limit

Your coding agent can't make new requests through Grid in a team when either of these happens:

* Your spend this month reaches your own limit in the team.
* Your team's total spend this month reaches the team-wide limit.

You can make requests again when an admin raises the limit or the next UTC calendar month starts. Baseten meters spend every 15 minutes, so your spend can exceed a limit before it takes effect.

Limits apply to requests made with Grid API keys you created. Your personal Baseten API keys aren't limited. For how admins set limits, see [Set spend limits and view usage](https://docs.baseten.co/grid/manage.md).

## Manage your Grid API keys

`baseten grid setup` creates a Grid API key for each machine you set up. Key values are never shown after creation.

**To find the Grid API key for a machine**:

Run the following command to list the Grid API keys you can manage. Admins can also see other developers' keys:

```sh theme={"system"}
baseten org api-key list --type grid
```

**To revoke the key for a lost or retired machine**:

Check the key's machine name and team, then replace `<prefix>` with that key's prefix and run the following command:

```sh theme={"system"}
baseten org api-key delete --prefix "<prefix>"
```

Coding agents that use a deleted key lose access until you run `baseten grid setup` again on that machine, which creates a new key. Delete each unwanted key by prefix; there is no delete-all option. For more information, see [Manage Grid API keys](https://docs.baseten.co/reference/cli/baseten/grid.md#api-keys).