Context Repo DocsSettings
Manage your API keys and permission scopes to integrate Context Repo with external tools and services.
The Settings page has two tabs: API Keys for managing programmatic access to your account, and Model Preferences for configuring default AI model settings (coming soon).
API Keys
API keys let external tools — like the Chrome Extension, MCP clients, and custom scripts — access your Context Repo data. You can create multiple keys with different permission scopes and revoke any of them at any time.
Creating an API Key
Click New API Key in the top-right corner of the API Keys tab to open the creation dialog. You'll see these fields:
| Field | Required | Description |
|---|---|---|
| Name | Yes | A label to help you remember what this key is used for (e.g., "Chrome Extension" or "CI Pipeline") |
| Permissions | Yes | One or more scopes that control what this key can access (see Permission Scopes below) |
| Expires | No | An optional expiration date — if left blank, the key doesn't expire |
After you click Create, the full API key is displayed once. Copy it immediately and store it somewhere safe — you won't be able to see the full key again.
Treat your API keys like passwords. Don't share them in public repositories, chat messages, or unencrypted files. If a key is compromised, revoke it immediately and create a new one.
Permission Scopes
Each API key is assigned one or more permission scopes that control what it can access. Four scopes are available — one read and one write per resource:
| Scope | Label | What It Allows |
|---|---|---|
prompts.read | Prompts — Read | List, read, search, and inspect prompt versions |
prompts.write | Prompts — Write | Create, update, delete, and restore prompt versions. Implies prompts.read. |
documents.read | Documents & Collections — Read | List, read, deep-search, and export documents and collections |
documents.write | Documents & Collections — Write | Create, update, delete, restore versions, scrape URLs, and manage collection memberships. Implies documents.read. |
The dialog has two pickers — one for Prompts and one for Documents & Collections — each with three options: None, Read, or Write. Selecting Write automatically grants the matching read access; you don't need to select both.
The Chrome Extension scrapes and saves web pages to your account, so it needs documents.write (which already includes documents.read). For full read-and-write access from MCP clients and other integrations, choose Write on both pickers.
Viewing Your Keys
The API Keys tab displays a table of all your active keys. Each row shows:
- Name — the label you gave the key when you created it
- Permissions — badges showing which scopes are assigned
- Created — when the key was created
- Last used — the most recent time the key was used to make an API call
- Expires — the expiration date, if one was set
Revoking a Key
To revoke an API key, click the delete icon on the key's row in the table. You'll see a confirmation dialog before the key is permanently deactivated.
Revoked keys stop working immediately — any tool or integration using that key will receive authentication errors until you provide a new one.
Model Preferences
Model Preferences is coming soon. This tab is currently disabled. Once available, it will let you configure default provider and model selection settings for your workspace tools.
Related Pages
Search
Find prompts, documents, and collections across your workspace using AI-powered semantic search or fast keyword matching.
Content Formats
Context Repo accepts both Markdown and HTML as first-class content. Markdown is optimized for agent consumption — lower tokens, faster generation, cheaper embeddings. HTML is optimized for human viewing — rich visuals, styled layouts, shareable reports.