API & Key Management
Manage personal API keys, org API keys, and service connections
This page separates user-level keys from organization-level API access.
Core functions
- personal API keys for users
- organization API keys (User Management API, if enabled)
- connection management for integrated services and OAuth-based MCP connections
Personal API keys require an organization flag that's disabled by default. It's enabled automatically as soon as your organization completes or upgrades a self-service Stripe subscription; for trial or invoice-billed Enterprise/Pilot organizations, our team is happy to help enable it.
Attention
Organization API keys aren't for chat completions. They're scoped exclusively to the User Management API (user administration), not chat requests. For chat completions, use a personal API key.
Admin practice
- rotate keys regularly
- grant API access only for concrete integration needs
- revoke unused keys quickly
External provider keys
Workspace admins can store their own API keys for external translation services (e.g., DeepL). See Translation Settings for details.