API Keys
What are API Keys
API Keys are tokens that authenticate requests to Orq.ai. A key covers one project, or every project in the workspace when created without one through the API. Its permissions limit what it can do. The API Keys create sheet always makes a single-project key and requires a Project, while the API accepts an omittedproject_scope for a key that reaches every project. Registering an MCP Gateway OAuth client on the OAuth Clients tab also mints a key, scoped to all projects. The create sheet defaults Owned by to You, a user key, while the API defaults an omitted owner to a service account.
User and Service account keys are chosen by the key’s owner. A Managed key comes from an MCP Gateway OAuth client instead.
User keys
Tied to a specific user account. Automatically revoked if the user is removed from the organization or the project one of their keys is bound to. Use user keys for personal use and local development.Service account keys
Not tied to any individual user, with a lifecycle independent of user membership. Only workspace admins can create service account keys. Use service account keys for production systems, so access does not break when a team member leaves.Viewing API Keys
Navigate to Settings > API Keys to see all keys across projects. The table shows the following columns:Creating an API Key
Open the creation panel

The Create new secret key sheet.
Choose an owner
Set name and project
Set permissions
Set expiration (optional)
Create and copy the key

The Save your key dialog appears once after creation.
Permissions
Restricted permission resources
Restricted permission resources
Managing Keys

The API Keys management table showing all keys, their type, status, permissions, and actions.
- Edit: update the name, permissions, or expiration date. The owner type cannot be changed after creation.
- Duplicate: opens the creation panel pre-filled with the key’s current settings.
- Delete: permanently removes the key. This cannot be undone.
Management Keys
Overview
Use cases
- Automating workspace provisioning via the API.
- Delegating API key rotation to a deployment pipeline without granting full admin access.
- Letting a billing automation script read and update Budgets without exposing API key management.
Workspace administration endpoints
API keys cannot administer API keys or Budgets, so those two families need a Management Key. Project and Smart Router management is open to both key types: an all-projects API key with write access to theproject and smart-router capabilities can create, update, and delete them, a single-project key cannot, and a Management Key needs the project or smart-router write grant to do the same.
View Management Keys
Open Management Keys in the Settings sidebar, under Organization, to view all keys in the workspace.
The Management Keys list showing key name, status, permission mode, and creator.
- Edit: open the edit panel to update the key’s name, permissions, or expiration date.
- Duplicate: create a new key with the same permissions.
- Delete: permanently remove the key from the workspace.
Create a Management Key
Open the creation panel

The Create new key panel with fields for name, permissions, and expiration date.
Enter a name
Set permissions
Set expiration (optional)
Create and copy the key
Permission modes
Capabilities
The Restricted mode shows one row per capability. None grants no access to that capability, Read lists and views its resources, and Write also creates, updates, and deletes them. A ✗ marks a level the picker omits for that capability, which then takes only None or Read.Manage keys programmatically
Create, update, revoke, and delete API Keys and Management Keys with the API instead of the console. The full endpoint reference is on the API Keys reference and Management Keys reference pages.Authenticating with a Management Key
Key management requests authenticate with a Management Key, never an API key. API Keys are inference credentials scoped to project resources and cannot administer keys.- Pass a Management Key as the bearer token, or as the SDK API key.
- A Management Key with the
api-keywrite grant can list, create, update, revoke, and delete API Keys.api-keyis the capability id behind the API keys row of the capability table above.
api_keys / apiKeys and management_keys / managementKeys: API Keys SDK, Management Keys SDK.
Key lifecycle in code
These examples use a Management Key asORQ_API_KEY.
owner and constraints to POST /v2/api-keys:
owner.type is service_account, which is the default, or user, which takes the user_id of a workspace member: { "type": "user", "user_id": "<member id>" }. constraints.expires_at must be in the future, and the key stops authenticating once it passes. The top-level expiration field is the legacy spelling of the same expiry; prefer constraints.expires_at.
Create a project-scoped key with restricted permissions:
Project scope
project_scope decides which projects the key reaches. On create, omit it and the key reaches every project in the workspace.
mode takes the short values all and single, or the enum values PROJECT_SCOPE_MODE_ALL and PROJECT_SCOPE_MODE_SINGLE. The nested spelling reaches the same scopes: {"all": {}} or {"single": {"project_id": "..."}}. Send one spelling per request.
projects is the legacy single-element array that older clients send instead of project_scope. It sets a single-project scope, and when a request carries both fields they must name the same project.
Permission model
permission_mode selects the preset:
restricted, the access map assigns a level to each domain. Write includes read:
GET /v2/api-keys/capabilities returns each domain with its id, display name, group, and read / write availability. Use the catalog to discover grantable domains at runtime instead of hard-coding the list.
The access keys are the id values the catalog returns (responses, model), not the display_name values (Responses, Models). For example, a restricted key that may run Responses and read the model catalog in every project:
The secret is returned once
The create response returns the raw token exactly once, in thesk-orq-<id>-<secret> format. Store it immediately: the API stores only a displayable token_prefix and a hash of the secret, so list and retrieve responses never include the raw token. Their token field carries a display value instead.
For how every other kind of secret is stored, read, and rotated, see Secrets management.