altllm-portal-billing

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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

AltLLM Portal Billing

Balance, promo, transaction history, and usage analytics 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
`credit`	Current Portal balance, expiry, and allowed models
`redeem-promo`	Redeem a promo code
`transactions`	Billing transaction history with pagination and type filters
`usage-summary`	Current calendar-month summary
`usage-timeline`	Daily usage history
`usage-by-model`	Usage grouped by model
`usage-by-key`	Usage grouped by API key

Rules

These commands use the saved Portal session token.
History commands mostly return raw Portal API JSON.
credit is the current CLI inspection path for plan/model-access metadata returned by Portal, including Business/Flex fields such as subscription_tier: "flex" when present.
transactions supports --page, --limit, and --type.
usage-summary currently reflects the current calendar month only.
usage-timeline, usage-by-model, and usage-by-key default to the current UTC month when no date flags are passed.
Usage commands support either --month or a complete explicit date range.
balance is an alias for credit.

Reference

See references/cli-reference.md for filters, examples, and representative outputs.

Repository: internet-court/internet-court-skill
Path: vendored/altlayer/altllm-portal-billing/SKILL.md
Commit: fa89195

Last updated: 4 days ago
First committed: 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.