--- sidebar_position: 10 title: Pod statements description: What each pod cost, day by day, from the billing ledger. The statement stays available after the pod is removed. --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.lium.io/llms.txt > Use this file to discover all available pages before exploring further. # Pod statements A **statement** is the list of charges for one pod, read from the billing ledger. The ledger keeps every charge after the pod is removed, so the statement of a removed pod reads the same as the statement of a running one. ## Where to find it - **Billing page, "Pods in this period"**: every pod you were charged for in the selected period, removed pods included. The period is the same date range as the daily chart above it (the last month by default). Expand a pod to see its per-day rows. The table lists pod charges only. Volume charges, and charges for pods removed before the ledger started keeping the pod, stay in the daily chart but not in the table, so the two totals can differ. Old charges are not rewritten; a pod's statement starts with its first charge after that change. - **Your Pods → a pod's menu → Billing statement**: opens `/your-pods//statement`. The link keeps working after you remove the pod, so you can bookmark it before `rm`. - **Your Pods** shows a **Statements for removed pods** link next to the pod count. The empty state says the same when you remove your last pod. - If you open the page of a removed pod, the **404** message links to its statement. ## What a statement shows | Field | Meaning | |-------|---------| | Total | Sum of the pod's ledger rows. This is the amount your balance was debited for the pod. | | Time billed | Sum of the seconds charged, shown as `1d 2h 3m`. | | Price | The hourly price. Two values with an arrow (`$0.25/h → $0.30/h`) mean the price changed during the rental; each segment lists its own seconds and amount. | | GPU | GPU count and model, for example `2× H100`. For a removed pod this comes from the last ledger row. | | Rented / Removed | Rental start and end. A removed pod also shows why it ended: removed by you, scheduled termination, insufficient balance, node went offline, node reclaimed by its provider, price change, marked broken by the provider, rent failed. Any other reason is shown as the API returns it. | | Billed until | On a running pod, the end of the last settled interval. A running pod lags the clock by at most one 5-minute charge. | | Per day (UTC) | One row per UTC day: time billed, `$/h`, amount, billed until. A day gets a second row when the platform closed the first one early. On a removed pod, the last row also holds the final settlement made at removal. | A pod that has not been charged yet says `Nothing billed yet — the first charge lands within five minutes of the pod running.` Amounts are shown with two to four decimals, so a single 5-minute charge is readable. The per-day rows and the total come from the same ledger rows; the total is the exact sum, and the rows are rounded for display.
For agents and automation: API Two routes under `https://lium.io/api`, both with a session or an `X-API-Key` header: - `GET /billing/statement?start_day=YYYY-MM-DD&end_day=YYYY-MM-DD`: every pod in the period, most recently billed first. Both days are inclusive UTC days and optional. - `GET /pods/{id}/statement`: one pod, before or after removal. `GET /billing/statement` returns `start_day`, `end_day`, `total` and `pods`. Each pod, and the body of `GET /pods/{id}/statement`, is one `PodStatement`: `pod_id`, `pod_name`, `gpu_name`, `gpu_count`, `executor_id`, `created_at`, `removed_at`, `close_reason`, `removed`, `billed_seconds`, `billed_until`, `total`, `price_segments` (one entry per distinct `$/h`) and `days` (per UTC day, oldest first: `billing_day`, `amount`, `billed_seconds`, `price_per_hour`, `billed_until`). Both routes read the active workspace's ledger when you are in one, and your own account's otherwise. `GET /pods/{id}/statement` answers `404` when that account has neither the pod nor a charge for it. `GET /pods/{id}` keeps answering `404` for a removed pod; use the statement route for a pod that is gone.