Key format and modes
| Mode | Prefix | Use |
|---|---|---|
| Live | sk_live_ | Normal API access for a workspace. |
| Test | sk_test_ | Test-mode API access where supported. |
Scopes
Scopes determine what the key can do.| Scope | Use |
|---|---|
models:read | List available active agent models. |
responses:write | Create, retrieve, and cancel responses. |
files:read | Read response files and file content. |
agents:read | List and inspect agents. |
agents:write | Create, update, archive, and run agents. |
runs:read | List and inspect automation runs. |
runs:write | Control run execution. |
env_vars:read | List environment variable metadata. |
env_vars:write | Create, update, and delete environment variables. |
env_vars:reveal | Reveal secret environment variable values. |
github:read | Read GitHub connection status. |
github:write | Connect and update GitHub authorization. |
api_keys:manage | Create, rotate, and revoke API keys through the API. |
Runtime-capable scopes
Salambo treats these scopes as runtime-capable:responses:writefiles:readruns:write
Last used timestamp
When a key successfully authenticates, Salambo updates itslast_used_at timestamp on a best-effort basis. A recently used key can show a recent last-used time even if the request later fails a runtime readiness check.
Security practices
- Store API keys in environment variables or a secret manager.
- Do not commit secrets to source control.
- Use separate keys per environment and integration.
- Give each key only the scopes it needs.
- Revoke keys that are no longer used.