Skip to content

internet-court/internet-court-skill / vendored/altlayer/altllm-portal-api-keys

altllm-portal-api-keys

Verified

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.

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

CommandPurpose
list-api-keysList active and disabled keys
create-api-keyCreate a new key, optionally with a model allowlist
get-api-keyInspect one key
update-api-keyRename a key, change status, or replace the model allowlist
revoke-api-keyPermanently 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.

Reference

See references/cli-reference.md for command examples and representative responses.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall