Start a fresh conversation. Replace the highlighted placeholders.
Use altllm-portal-api-keys to create an API key named [key name and optional model allowlist] after I explicitly confirm; return the key securely, noting it is shown only once.
Required inputs
[key name and optional model allowlist]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: altllm-portal-api-keysdescription: Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.user-invocable: true
AltLLM Portal API Keys
Portal API key lifecycle management for the local altllm CLI.
Shared Setup
Before the first altllm command in a fresh checkout, read and follow:
../_shared/preflight.md
../_shared/session-and-target.md
Command Index
Command
Purpose
list-api-keys
List active and disabled keys
create-api-key
Create a new key, optionally with a model allowlist
get-api-key
Inspect one key
update-api-key
Rename a key, change status, or replace the model allowlist
revoke-api-key
Permanently revoke a key
Rules
create-api-key returns the full key only once.
If no model allowlist is passed, the Portal API applies its default AltLLM model set.
Key permissions narrow accessible models, but gateway balance and tier checks still apply.
Flex users can allowlist normal AltLLM models and Flex-only altllm-flex-* models; backend access checks remain authoritative.
update-api-key --status disabled is reversible.
revoke-api-key is permanent.
keys is an alias for list-api-keys.
Known Production Limitation
The single-key Portal API routes are currently broken in production.
Affected commands:
get-api-key
update-api-key
revoke-api-key
Commands that still work:
list-api-keys
create-api-key
Do not create temporary production smoke keys unless revoke-api-key is healthy or an approved cleanup path exists.