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

# Anthropic

> Bring your own Anthropic API key to KnoxCall — what the workspace-scoped key powers (anomaly analysis, spec analysis, the workflow copilot), how to scope it with a Workspace and spend limit, and the difference from AI Gateway upstream keys.

# Anthropic

KnoxCall's AI features run on Claude. Which key they use depends on the scope:

| Scope               | What the key powers                                                                                                                                                                                                                                                                                                                                                       |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **This tenant**     | Everything AI that KnoxCall does *for your workspace*: alert anomaly analysis, OpenAPI spec analysis, collection analysis, the workflow copilot, and the AI Gateway's system agent. **There is no fallback to a platform key** — until you save your own, those features tell you a key is required. Your usage is billed to your Anthropic account, never to KnoxCall's. |
| **Global defaults** | The platform's own AI: the support assistant, blog autopilot and AI-visibility probes. On KnoxCall Cloud this is KnoxCall's key; a self-hosted deployment that wants those features saves its own here.                                                                                                                                                                   |

<Note>
  This is **not** where the AI Gateway gets keys for the models it proxies. Upstream provider keys for the gateway are attached to the gateway itself — see [Bring your own key](/ai-gateway/byo-key).
</Note>

## 1. In the Anthropic Console

Anthropic API keys carry no scopes; you scope them by **Workspace**, which also isolates rate limits and spend.

1. [console.anthropic.com](https://console.anthropic.com) → **Settings → Workspaces → Create workspace**, dedicated to KnoxCall.
2. On that workspace set a **monthly spend limit** — the key is used by unattended analysis, not only by people clicking buttons.
3. **Settings → API keys → Create Key**, attached to that workspace. Copy the value (`sk-ant-api03-…`) — shown once.

## 2. Enter it in KnoxCall

**Settings → Integrations** → scope → **Anthropic** → *Configure*:

| Field                  | Value                                                                                                                                      |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **API key**            | `sk-ant-…`                                                                                                                                 |
| **Model** *(optional)* | Leave blank. KnoxCall picks a current model centrally and moves it forward when a new one ships; set this only to pin a specific model id. |

**Save credentials.**

## 3. Verify

Open an alert and run **AI analysis**, or ask the workflow copilot for a suggestion. A wrong key fails there with an authentication error from Anthropic. The operator console's *Test connection* lists models with the stored key.

## Things that bite

* **Rotation.** Create the new key, save it here, then delete the old one in the console. The form keeps the stored key when the box is left blank, so a public-only edit (changing the model) never drops it.
* **Self-hosted environment fallback.** For the Global defaults row, a stored key wins over `ANTHROPIC_API_KEY`; the variable is used only when no row exists.
* **Spend limits are yours to set.** KnoxCall applies its own per-workspace AI rate limits, but the bill is on your account.

## Related

* [AI threat detection](/security/ai-threat-detection) — what anomaly analysis looks for
* [Workflows — AI](/workflows/ai) — the copilot and AI steps
* [OpenAI](/integrations/setup/openai) — the platform fallback provider