Skip to main content

lium billing

The account's charges as the billing ledger recorded them: what was actually debited from the balance, per pod and per day.

lium billing history [OPTIONS]

lium billing history​

Every pod the account paid for in the period, removed pods included, most recently billed first. A pod's total is the sum of its per-day ledger rows, which is the amount the balance was debited (unlike lium spend, which estimates). The API key needs the read scope.

Options​

FlagEffect
--from YYYY-MM-DDFirst UTC billing day to include (inclusive)
--to YYYY-MM-DDLast UTC billing day to include (inclusive)
--key NAME|IDOnly the pods rented through this API key. A name needs lium workspaces login; an id does not
--format [table|json]Output format (default table)
--jsonSame as --format json

The table has one row per pod: Pod, GPU, Billed (hours), Total, From and To (UTC; running for a pod that is still up), and a Key column when the charges name the key they came through. The line under it gives the total.

--key filters only on a server that records which key each charge came through. A server that does not answers for every pod: the CLI then says the figures are the whole account's instead of heading them "through key …", and in JSON api_key_filter.applied is false.

--format json prints the server's statement: total and pods, each pod with its days; with --key also api_key_filter (api_key_id, applied).

Examples​

lium billing history                                       # Every pod charged
lium billing history --from 2026-09-01 --to 2026-09-21     # One period
lium billing history --key agent-1 --format json | jq '.total'

A --from or --to that is not a YYYY-MM-DD day, or a --to before --from, exits 2 before any call is made.

See also​