Skip to main content

​
Anthropic

KnoxCall’s AI features run on Claude. Which key they use depends on the scope:
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.

​
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 → 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: 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.