> For the complete documentation index, see [llms.txt](https://docs.otari.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otari.ai/how-to-guides/manage-provider-keys.md).

# Manage provider keys

Add provider keys at the organization level, then control which workspaces can use them.

For background, see [Provider Keys](/learn/provider-keys.md).

***

### Add a provider key <a href="#h_17846d81b3" id="h_17846d81b3"></a>

There are two ways to get provider access:

#### Otari-managed keys

These are Otari's pre-provisioned keys you can use without bringing your own key material. Otari handles the upstream credential, and requests on them are billed to you and spend against your budget. To create an Otari-managed key:

1. From the main dashboard, click on **API Keys**.
2. Click on **Create Key** in the top-right corner.
3. Give the key a name and, if needed, set an expiration date. By default, the key inherits your existing model access, but you can limit it to specific models. To customize model access, click **Advanced** and select the models you want the key to use.
4. Copy the token right away. It is only shown once.

{% hint style="warning" %}
This is the only time the key will be shown. Copy it now if you need it later.
{% endhint %}

#### Your own keys

Bring your existing provider API keys and let Otari use them on your behalf. The upstream provider bills you directly, and Otari adds no per-token routing charge. To add your own key:

1. From the main dashboard, click **Organization**.
2. Select **Providers**.
3. Click **Add provider key** in the top-right corner.
4. Select the **Provider** from the dropdown.
5. Enter a **Key Name** to easily distinguish multiple keys for the same provider, such as `production`, `staging`, or `backup`.
6. Paste your **API key**.
7. Click **Add Provider key** to save it.

***

### Set a default key per provider <a href="#h_07616d7e56" id="h_07616d7e56"></a>

If you have multiple keys for the same provider, mark one as the default so workspaces inherit it automatically.

1. In the **Provider** tab, find the keys for the provider.
2. Click on the **star icon** to set it as the default key you want workspaces to inherit.

Workspaces inherit the organization default per provider unless you define a different key.

***

### Control workspace access <a href="#h_1839be0f9b" id="h_1839be0f9b"></a>

Once a provider key has been added at the organization level, open the relevant workspace and click **Edit** (the pencil icon) to manage its provider access. For each provider, you can:

* Select **Following the organization** to allow access to all providers defined at the organization level.
* Select **Never use this key** to prevent the workspace from using a specific provider key.
* Select **Always use this key** to ensure the workspace uses a specific provider key. You can further restrict access to specific models from that provider by selecting the model you want to make available and clicking **Allow**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otari.ai/how-to-guides/manage-provider-keys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.