# API keys

> Create, limit, roll, disable and delete DigitSpace API keys in the dashboard, and see what each key has spent.

Source: https://digitspace.ai/docs/dashboard/api-keys · Last checked: 2026-10-31

Open **API keys** in the project. The page shows how many keys the organisation uses out of its plan's allowance: 5 on Free, 20 on Pro and 500 on Enterprise.

## Create a key

Choose **Create an API key** and fill in:

| Field               |                                                                           |
| ------------------- | ------------------------------------------------------------------------- |
| **Name**            | What it's for, such as "Production server".                               |
| **Expires**         | Never, 7, 30 or 90 days, or a date you pick.                              |
| **Total limit**     | Dollars the key may spend in total. Empty for no limit.                   |
| **Repeating limit** | Dollars per period, resetting every so many hours, days, weeks or months. |

The secret is shown once. Copy it, then confirm with **I've saved it**. DigitSpace stores only a hash, so a lost secret can't be shown again; roll the key instead.

## Manage a key

Each key's menu has:

- **Rename**, **Spend limits** and **Change expiry**.
- **Access rules**, to allow or block models, providers, prices and IP addresses. See [Access rules](/docs/control/access-rules).
- **Disable** and **Enable**. A disabled key returns `401` until it's enabled again.
- **Roll secret**: a new secret for the same key. The old one stops working at once.
- **Delete**.

Each row shows the key's status (Active, Disabled or Expired), its total spend and its spend this period. Open a key to see its requests, spend, tokens, error rate and models used over time.

Keys marked **Managed** are made by DigitSpace, for the playground, and have no menu.

## Who sees which keys

Owners, admins and project admins see every key in the project and can switch between **All keys** and **My keys**. Developers see and manage only their own, within the budget an admin gave them; see [Budgets](/docs/control/budgets#on-a-member).