# Management keys

Source: https://provod.ai/en/docs/management-keys

A management key lets your server manage inference keys and read workspace spending. Use an ordinary API key to call models.

## Create a management key

1. Open [Management keys](https://app.provod.ai/management-keys) in the cabinet.
2. Select your personal workspace or organization.
3. Create a key with a descriptive name.
4. Save the key secret in your server’s secret store.

Each key is bound to one workspace. Create another key for a different workspace. Do not use scope or `X-Org-Id` to switch it. Keep the secret out of browser code and repositories.

## API reference


| Endpoint                   | Purpose                                                         |
| -------------------------- | --------------------------------------------------------------- |
| `GET /v1/key`              | [Get current key](/en/docs/key-current)                         |
| `GET /v1/keys`             | [List API keys](/en/docs/keys-list)                             |
| `POST /v1/keys`            | [Create an API key](/en/docs/keys-create)                       |
| `GET /v1/keys/{hash}`      | [Get an API key](/en/docs/keys-get)                             |
| `PATCH /v1/keys/{hash}`    | [Update an API key](/en/docs/keys-update)                       |
| `DELETE /v1/keys/{hash}`   | [Delete an API key](/en/docs/keys-delete)                       |
| `GET /v1/credits`          | [Get top-ups and spending](/en/docs/credits)                    |
| `GET /v1/analytics/meta`   | [Get analytics metadata](/en/docs/analytics-meta)               |
| `POST /v1/analytics/query` | [Query analytics](/en/docs/analytics-query)                     |
| `GET /v1/activity`         | [Get daily activity](/en/docs/activity)                         |
| `GET /v1/generation`       | [Generation metadata and charges](/en/docs/generation-metadata) |


## Choose the credential


| Task                                                         | Credential                              |
| ------------------------------------------------------------ | --------------------------------------- |
| `POST /v1/chat/completions`, `/v1/responses`, `/v1/messages` | Inference key                           |
| `GET /v1/balance`, `GET /v1/usage`                           | Inference key                           |
| Key management and workspace reports                         | Management key                          |
| `GET /v1/key`, `GET /v1/generation`                          | Either kind, within its access boundary |


## Balance and spending

* **Available balance:** `availableBalance` in [GET /v1/balance](/en/docs/api-key-usage), after reservations.
* **Remaining key allowance:** `limit_remaining` and exact `spend_limits` amounts in [GET /v1/key](/en/docs/key-current). This is a key ceiling, not the workspace balance.
* **All-time top-ups and spending:** [GET /v1/credits](/en/docs/credits).
* **Individual request charge:** `usage.cost` and provod.billing.total\_charge. [JSON, SSE and disconnect recovery](/en/docs/generation-metadata).

## Permissions and revocation

Create and revoke management keys in the cabinet using a web session. Organization permissions are `managementKeys.read`, `managementKeys.create` and `managementKeys.revoke`; do not send them with Bearer requests. Public methods check the owner’s current access. Revocation is permanent.
