Management — API Key Management
Navigate to: Dashboard → API Key Management
What it shows: All LLM provider API keys (OpenAI, Anthropic, Google, Azure, etc.) stored in AgentWatch. Keys are encrypted at rest; only the last 4 characters are visible.
Important: These are the upstream provider keys AgentWatch uses to call LLMs — not the employee API keys used to authenticate requests to AgentWatch.
Step-by-step: Add a provider API key
- Click API Key Management in the sidebar.
- Click Add Key.
- Select the Provider (e.g.,
OpenAI). - Enter a Label (e.g.,
prod-openai-key-1). - Paste the API Key.
- Optionally set a Rate Limit (requests/minute) and Max Concurrency.
- Click Save.
- Click Test on the new key row — AgentWatch sends a minimal probe request to confirm the key is valid.
Step-by-step: Disable a key without deleting it
- Find the key in the list.
- Toggle the Enabled switch off.
- AgentWatch stops routing requests through this key immediately. Other enabled keys for the same provider continue working.
Step-by-step: Bulk operations
- Check the boxes on multiple key rows.
- Click Bulk Actions → Disable Selected or Delete Selected.
- Confirm the action.
Key status indicators:
| Indicator | Meaning |
|---|---|
| Green dot | Enabled and passing health checks |
| Yellow dot | Enabled but last health check returned a non-200 response |
| Red dot | Disabled or failed authentication |
| Grey dot | Never tested |
How to test:
- Add a key with a deliberately wrong API key string.
- Click Test — the row should show a red status with an error message.
- Replace with the correct key value (click Edit) and re-test — status goes green.
API endpoints:
| Method | Path | Purpose |
|---|---|---|
| GET | /api/providers/:id/keys |
List keys for a provider |
| POST | /api/providers/:id/keys |
Add key |
| PUT | /api/keys/:id |
Update label, rate limit |
| DELETE | /api/keys/:id |
Remove key |
| PUT | /api/keys/:id/toggle |
Enable/disable |
| POST | /api/keys/:id/test |
Test connectivity |