Usage and impact
Four views of your account: a summary, a per-call history, a per-key breakdown, and the environmental tally. Same data the dashboard shows, minus the chrome — readable from a terminal or a CI step.
Summary
melious usageTotals for the current period: requests, tokens, credits, environmental impact, a product breakdown, and your most-used models.
Pick a period:
melious usage --period day
melious usage --period week
melious usage --period monthHistory
Recent calls as a table:
melious usage history| Flag | Type | Default | Description |
|---|---|---|---|
--limit | int | 20 | Rows per page |
--product | string | — | Filter: inference, kit, engine, chat |
--model | string | — | Filter by exact model ID |
Examples:
melious usage history --product inference
melious usage history --model qwen3-235b-a22b-instruct
melious usage history --limit 50Per-key breakdown
melious usage keysRequests, tokens, credits, and last-used timestamp for each of your API keys. Useful when you're tracing spend back to a specific integration — or trying to work out which key you can safely rotate.
Environmental impact
melious usage envFour numbers and what they translate to in the real world:
- Carbon (g CO₂) with everyday equivalents
- Water (L) with household comparisons
- Energy (kWh) with device-hour equivalents
- Renewable energy share across the providers your requests hit
These are estimates, not telemetry from the data center floor — the methodology lives in Environmental impact. We're honest about the error bars there.
For per-response numbers from the terminal, use melious run --show-env on a single call, or flip stats.environment on in your config to get them on every run.