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

# API keys

> Create and revoke API keys for AI agents: viewer vs editor permission, name keys after the agent, the key is shown once, the prompt contains the real key.

An API key lets an agent or bot work in **one workspace** without a user account. Only workspace admins create and revoke keys.

## Create a key

**1. Open the API keys page**

Go to **Settings**, the API keys page.

**2. Click Create API key**

Enter a **Name** to recognise it, choose the **Permission**, click **Create**.

**3. Copy and save**

The **API key created** dialog shows the key and ready-made prompts per agent. Copy the prompt from the right tab, then click **I have saved the key**.

> [!WARNING]
>
> An API key is **shown only once** when created. Once you close the dialog you cannot view it
> again. The agent prompt **contains the real key**: treat it like a password and never paste it
> into public chats, tickets or git. If it leaks, revoke the key and create a new one.

## Viewer or Editor

| Permission | Can do | Use when |
| - | - | - |
| **Viewer** (read-only) | View channels, posts, publish status, the comment inbox | The agent only reports or monitors |
| **Editor** (read and write) | Everything a viewer can, plus publish/delete posts, first comments, replies, private replies, hide, mark as handled | The agent publishes or answers comments |

Give the lowest permission that works. A read-only agent should use Viewer.

## Name the key after the agent

Name each key after the agent that uses it, for example `claude-code-posting`, `grokbot-inbox`. The name shows in the comment inbox action history and as the creator in the content calendar, so you know which agent did what. Use one key per agent so you can revoke them individually.

## The key list

The table shows **Name**, **Key**, **Permission**, **Last used**, **Created**, **Status** (Active / Revoked). Revoke keys that have not been used for a long time or whose owner is unknown.

## Revoke a key

Click **Revoke** on the key's row and confirm. Every system using the key loses access immediately, which is also how you stop an agent.

## Limits

Each key may make up to **120 requests per minute**, counted across all actions. Beyond that you get a 429 error and the agent must wait and retry.

## Example key (fake)

```text theme={null}
smk_0a1b2c3d_<43-character secret string>
```


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