# API Keys

Use **API Keys** when you need credentials for calling Fetch Hive deployments from your own app or service. This page manages workspace API keys, not third-party provider keys for personal model usage.

## Overview

The page separates your **Default API Key** from any additional keys you create for specific environments or services. Additional keys appear in a table where you can search, filter, rotate, revoke, and review last-used activity.

Fetch Hive supports environment-specific keys, so you can keep **Production**, **Staging**, and **Development** access separate.

## How do I create an API key? <a href="#create-api-key" id="create-api-key"></a>

Open **Settings** in the sidebar, then click **API Keys**.

If the workspace does not have a default key yet, click **Create Default Key**.

If you want an additional key, click **Add API Key**.

Enter a name and choose the environment:

* **Production**
* **Staging**
* **Development**

Save the key. Fetch Hive then shows **Your New API Key**.

Copy the full key right away. The full value is only shown when the key is first created or rotated.

## How do I rotate or revoke a key? <a href="#rotate-or-revoke-api-key" id="rotate-or-revoke-api-key"></a>

Find the key you want to change in **Default API Key** or the table of additional keys.

Use **Rotate Key** when you want to replace the current secret with a new one.

Use **Revoke** when you want to disable a key and prevent future use.

Fetch Hive asks you to confirm either action before it proceeds.

## Why can I only copy part of a key? <a href="#copy-api-key" id="copy-api-key"></a>

After the creation or rotation dialog closes, the page keeps the masked key prefix for reference but usually no longer has the full key value available to copy.

That is why you should copy the full secret from **Your New API Key** before you close that dialog.

The masked display is still useful for confirming which key you are looking at and checking its environment, status, and last-used information.

## How is this different from provider credentials? <a href="#api-keys-vs-provider-credentials" id="api-keys-vs-provider-credentials"></a>

Workspace API keys authenticate requests to Fetch Hive deployments.

They are different from provider credentials you connect for **Personal** charge type. For that flow, use [Use your own API Key](/your-workspace/llm-providers.md) and [Integrations](/your-workspace/integrations.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fetchhive.com/your-workspace/api-keys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.