Rentals & Billing History

Every charge Grafilab makes against your account — a GPU rental, a renewal, a top-up, API usage — appears as a row in one table. This page explains how to read it, what the status colours mean, and how to get an invoice out of it.

My Instance shows only what is running right now. Once a rental expires, its card is gone; the money side of it is not.

The permanent record is on Billing, under Invoice History — “Your full billing statement record.” It’s a single table covering all products, and it loads by infinite scroll: keep scrolling and older rows keep arriving until you hit “You have reached the end”.

The columns are Date · Instance · Type · Description · Payment · Amount · Status · Invoice.

Column	What it tells you
Date	When the charge was raised.
Instance	The rental the charge belongs to, for compute rows. Blank for account-level rows such as top-ups.
Type	Which kind of transaction this is — rentals, renewals, top-ups, and API/inference usage.
Description	A longer line naming the node, template, or package involved.
Payment	How it was paid — from your credit balance, or by card.
Amount	The value charged. Each row carries its own currency, so a table can mix currencies if your wallet currency changed; read the symbol, don’t assume.
Status	Whether the money actually moved — see below.
Invoice	A download icon on rows that have an invoice.

The badge colour is the fastest way to tell whether something worked:

• Green — paid, success, succeeded, complete, completed, settled. The charge went through. For a rental, this is the row that pays for a running instance; for a renewal, the row that extends it.
• Amber — pending, processing, in_progress, open. The payment is still being confirmed. A card checkout you haven’t finished, or a renewal waiting on the payment provider, sits here. Wait rather than retrying — a second attempt can charge you twice.
• Red — failed, failure, error, unpaid, incomplete, canceled, cancelled, void. Nothing was charged, which also means nothing was delivered: no instance was launched and no rental was extended. Fix the payment method or top up, then run the action again.

Anything the console doesn’t recognise shows as a neutral grey badge.

Rows that can be invoiced carry a download icon in the Invoice column, with the tooltip Download invoice. Click it and the console builds a PDF in the browser and saves it.

If it fails you’ll get a toast reading “Could not generate the invoice.” with the reason appended. Reload the page and try once more; rows still showing an amber status may not have an invoice yet.

Clicking Renew on an instance card raises its own row here, separate from the original rental. The sequence is worth knowing:

1. You confirm the renewal, and the row appears — usually amber at first.
2. The payment settles and the row turns green.
3. Only then does Expire at on the instance card move to its new time.

So a renewal that looks like it “didn’t work” is normally a row that hasn’t gone green yet. Check the status here before renewing a second time. A red renewal row means the extension did not happen and the instance still expires at the original time.

For totals rather than individual rows, use the Usage This Month card at the top of the same Billing page. It breaks the month into exactly three lines — Compute, API / Token, and Subscription — with Monthly Spend above them and arrows to step through Previous month and Next month. GPU rentals and renewals land in Compute.

The figures are cached: a footnote reads “Updated every 30 min · UTC”, so a charge from the last few minutes may not be counted yet. If the breakdown can’t load it shows “Spending breakdown unavailable.” View inference usage jumps from there to the per-request view for the month on screen.