api_key_update
ManagementcatalogUpdate Project API Key Role
Not in the default tool list
This tool lives in the tool catalog. Discover it with scenario_tools_search (or enumerate everything with scenario_tools_list) and run it via scenario_tool_execute_write. To list every tool directly, connect with ?toolsets=full.
Change a project API key's role or scopes.
Args:
- project_id: required
- key_id: required — the key's id (apiu_...) or api_key_id (api_...), from api_keys_list
- role: required — 'admin', 'editor', 'reader', or a custom ';'-separated scope list (e.g. 'assets.read;models.run')
- team_id: optional — required for OAuth sessions
- response_format: optional — 'json' (default) or 'markdown'
Returns: {updated: true, key_id, role, manage_keys_url, note}. Name, status, and usage limits (maxConsumption) are portal-only — limits require an Enterprise plan and a human team admin.
Don't use when: Changing a human member's role — use project_members_update / team_members_update.
open-world
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| team_id | string | — | Team ID. Required if user belongs to multiple teams. |
| project_id | string | ✓ | Project ID. Get it from projects_list. |
| key_id | string | ✓ | The key's id (apiu_...) or api_key_id (api_...) — from api_keys_list. |
| role | string | ✓ | Built-in 'admin', 'editor', or 'reader', or a custom ';'-separated scope list (e.g. 'assets.read;models.run'). |
| response_format | enum(json | markdown) | json | Output format: 'json' for structured data, 'markdown' for human-readable text. |