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

# API keys

> Create organization API keys with read or write access, send them with your requests, and revoke them.

An API key lets a script, an app or an MCP client use SEOmator without signing in. Keys belong to the organization, not to a person, and a key only reaches the organization it was created in.

Owners and admins

What each role can do: [Members](https://docs.seomator.com/settings/members.md).

In the sidebar, click your name and select **Organization settings**, then click **API keys** in the settings sidebar.

![The API keys page with one Read and write key named Reporting script, never used, and its Revoke button](https://mintcdn.com/se-omator/LHKLDWeFBDdpYX2o/images/api-keys.light.png?fit=max\&auto=format\&n=LHKLDWeFBDdpYX2o\&q=85\&s=9e3b604c67bced979f9164475d18020c)

## Key list

Each key shows its name, its access, the first characters of the key, when it was created and when it was last used.

## Access levels

| Access | What the key can do |
| - | - |
| **Read only** | Read projects and reports. It can't change anything. |
| **Read and write** | Everything a read-only key can, plus project work: create, change and delete projects, prompts and competitors, start tracking and spend credits. |

No key can manage members, API keys or billing, whatever its access. Choose **Read only** unless the app needs to make changes.

## Create a key

**1. Open the form**

Click **New key**.

**2. Name it**

Enter a **Name** you will recognize later, such as the app that uses it.

**3. Choose its access**

Under **Access**, choose **Read only** or **Read and write**.

**4. Create it**

Click **Create key**.

**5. Copy it**

Click **Copy**, store the key, then click **Done**.

The key appears in the list.

> [!NOTE]
>
> The key is shown only once. Copy it before you click **Done**. If you lose it,
> revoke it and create a new one.

## Send the key

Send the key with every request, in one of these two headers:

```text theme={null}
x-api-key: sk_...
```

```text theme={null}
Authorization: Bearer sk_...
```

The same key works for the API and for MCP clients. To connect an AI tool with a key, see [MCP and AI tools](https://docs.seomator.com/agent/mcp.md#connect-with-an-api-key).

## Revoke a key

> [!WARNING]
>
> Apps using the key stop working right away. To use the API again, they need a
> new key.

**1. Start**

In the key's row, click **Revoke**.

**2. Confirm**

Click **Revoke** in the confirmation.

The key disappears from the list.

## Related

> [card] [MCP and AI tools](https://docs.seomator.com/agent/mcp.md)
>
> Connect Claude, ChatGPT and other AI tools.

> [card] [Members](https://docs.seomator.com/settings/members.md)
>
> Roles and who can manage keys.


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