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

# AI assistants and API keys

> Connect AI assistants, see what has access, and manage REST API keys.

Open **Settings → API & AI assistants** in the dashboard. It has two parts: AI assistants, which sign in, and API keys, which are for the REST API.

| Plan | AI assistants ([MCP server](/mcp/introduction), read-only) | [REST API](/api-reference/introduction) keys |
| - | - | - |
| Free trial | | |
| Basic | ✓ | |
| Growth | ✓ | |
| Enterprise | ✓ | Up to 25 |

## AI assistants

Claude, ChatGPT, Claude Code, Cursor, VS Code and other MCP clients connect by signing in with RankRaft. See [Connect your AI assistant](/mcp/connect). Assistants get **read-only** access, and any member can connect one.

### Connected assistants

Every member sees every connected assistant: its name, who connected it, when it was connected and last used, and how many tool calls it made in the last 30 days.

Click **Disconnect** to remove one. It stops working on its next request. Members can remove assistants they connected; owners can remove any. An assistant also stops working when the person who connected it leaves the organization.

## API keys (Enterprise)

Keys are for the [REST API](/api-reference/introduction): scripts, data warehouses and your own tools. They don't work with the MCP server.

### Who can do what

| | Owner | Member |
| - | - | - |
| See the list of keys | ✓ | ✓ |
| Create a key | ✓ | |
| Revoke a key | ✓ | |
| See a key's secret | Once, when creating it | Never |

Keys belong to the organization, not to the person who made them. A key keeps working if its creator leaves the team; revoke it if it should not.

### Create a key

1. Click **Create key**.
2. Give it a name that says where it will live, e.g. *Looker sync* or *Prompt sheet*.
3. Choose an expiry: 30, 90, 180 or 365 days. Every key expires; there is no never-expiring option.
4. Choose access:
   * **Read only** — every report, site, prompt and action endpoint.
   * **Read and manage prompts** — also create, update, activate and disable prompts.
5. Copy the key. It starts with `rr_api_` and is shown **once**. RankRaft keeps only a fingerprint and cannot show it again.

<Warning>
  Treat a key like a password. Store it in a secret manager or environment variable, never in a browser, a mobile app or a public repository. Keys starting with `rr_api_` are easy for secret scanners to spot.
</Warning>

### The key list

| Status | Meaning |
| - | - |
| **Active** | Working. |
| **Expiring soon** | Expires within 14 days. Create a replacement now. |
| **Expired** | Stopped working on its expiry date. |
| **Revoked** | Turned off by an owner. |

### Rotate a key

1. Create a new key with the same access.
2. Deploy it wherever the old key is used.
3. When **Last used** on the old key stops moving, revoke it.

### Revoke a key

Click **Revoke** and confirm. The key stops working within seconds and cannot be turned back on.

## When access stops

Connected assistants stop working when billing is paused or canceled, or the account returns to the free trial. API keys stop working in those cases and whenever the organization leaves Enterprise. Both start working again, unchanged, when the plan is restored and they have not expired.


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