altllm-portal-auth
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.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/altllm-portal-auth && cp -r /tmp/altllm-portal-auth/vendored/altlayer/altllm-portal-auth ~/.claude/skills/altllm-portal-authSKILL.md
# AltLLM Portal Auth Wallet login and session bootstrap for the local `altllm` CLI, including external signers such as Privy. ## 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 | |---|---| | `login-wallet --private-key-env <name>` | Sign in with a locally available private key from an environment variable | | `login-wallet --private-key-file <path>` | Sign in with a locally available private key from a file | | `login-wallet --private-key <hex> --allow-unsafe-private-key-argv` | Sign in with an inline private key when argv exposure is explicitly accepted | | `login-wallet --prepare` | Fetch a challenge for external signing | | `login-wallet --nonce <nonce> --signature <sig>` | Verify an externally signed challenge and save the session | | `status` | Show saved Portal session user and target URL status without exposing the token | | `logout` | Remove the local saved Portal session file | ## Rules - Do not assume the CLI must control the wallet private key. - If the wallet can sign the challenge message, use the prepare + verify flow. - External signers such as Privy are valid as long as they return a standard wallet signature for the challenge. - If neither a local private key nor `--signature` is available, return the challenge payload and stop. - Before local auto-signing, validate that the returned challenge matches the requested wallet, chain, and expected AltLLM login challenge structure. - For non-default, non-loopback API hosts, prefer `--prepare` and external signing instead of local auto-signing. - Current backend support is still limited to EVM addresses and Ethereum-style signatures. - Save the resulting session to `~/.altllm/portal-cli-session.json` unless overridden. - Use `status` or its `whoami` alias to confirm the saved user and target URL before running live commands. - `logout` only removes the local session file. It does not revoke API keys. ## Reference See [references/cli-reference.md](references/cli-reference.md) for commands, payloads, and troubleshooting notes.
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 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.
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.