altllm-portal-api-keys
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.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/altllm-portal-api-keys && cp -r /tmp/altllm-portal-api-keys/vendored/altlayer/altllm-portal-api-keys ~/.claude/skills/altllm-portal-api-keysSKILL.md
# 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. ## Reference See [references/cli-reference.md](references/cli-reference.md) for command examples and representative responses.
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), agent jobs (ERC-8183), machine payments (MPP, AP2), supervision of agent behavior, revocation, verification, or dispute resolution (GenLayer) — even if they never say "Internet Court". Routes to the vendored protocol skills and connector skills in this package.
Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority. Use when an agent needs to design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling that turn a GenLayer agent-performance review into ERC-7710 revocation or policy changes.
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.
Use this umbrella skill when the request spans multiple AltLLM Portal CLI domains, or when you need to navigate the local altllm CLI in this repository across auth, API keys, billing history, NOWPayments payment links, and related x402 Portal top-up guidance.