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

# API keys

> Create, limit, rotate and revoke the keys your clients use.

Your clients authenticate with a nemonist API key, sent as a bearer token:

```bash theme={null}
Authorization: Bearer $NEMONIST_API_KEY
```

Create keys on the **API keys** page of a [workspace](https://nemonist.com/docs/concepts/workspaces.md). Create one key for each client or teammate, so you can see each one's usage and stop one without touching the others.

## Limit a key

Open a key to set:

* **A spending limit.** Requests are refused once the key has spent this much in the period. It counts what nemonist charges plus what requests cost on your own provider keys or Router key, at the provider's price, so on the Free plan with your own keys the limit still caps your provider bill. A limit caps what a leaked key can spend.
* **Allowed models and providers.** Leave a list empty to allow anything. Requests for other models are refused; provider rules pin routing to those providers.
* **An expiry.** An owner can require every key to expire within a maximum lifetime under [Privacy](https://nemonist.com/docs/concepts/privacy.md).

To restrict a group of keys at once, use [Guardrails](https://nemonist.com/docs/concepts/guardrails.md).

## Memory off for an app

A key for an app that calls the API, rather than a coding agent, should have memory off: check **No memory, for an app that calls the API** when you create it, or choose **Turn off** under **Memory** on the key's page. Its requests are sent as your code wrote them, with no memory and no added tokens, even with `tools`. From code, send `"memory_off": true` to `POST /keys` or `PATCH /keys/{hash}`.

## Jobs permission

A key can run [cluster jobs](https://nemonist.com/docs/concepts/credits.md#managed-compute) only with the jobs permission. Check **Jobs: may run jobs on the cluster** when you create the key, or choose **Allow** under **Jobs** on the key's page. A new key does not have it unless you ask for it, and a management key never does; keys created before November 18, 2026 keep it. Without it, an agent using the key can still read job status, logs and outputs, but cannot submit, rerun, run, cancel or upload. From code, send `"jobs": true` to `POST /keys` or `PATCH /keys/{hash}`.

## Rotate or revoke

* **Regenerate** gives the key a new secret. The current one stops working immediately, so update every app that uses it. Name, rules, limit and usage stay.
* **Delete** stops every request using the key. This cannot be undone.

The secret is shown once, when you create or regenerate the key. Copy it then.

## Management keys

On the Standard plan and above, a management key manages keys through the [API](https://nemonist.com/docs/api-reference/overview.md) (`/keys`) and cannot make model requests.

## In CI

Rather than storing a long-lived key in CI, let the job exchange its own identity token for a key that lasts an hour. See [Workload identity](https://nemonist.com/docs/enterprise/workload-identity.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.