Usage and costs

Every charge Nodus makes is backed by usage records: one line per meter, per object, per window. This page shows how to read them, group them and export them.

See what a run cost

Each compute object shows its cost so far in status.cost:

nodus get job train-llama -o jsonpath='{.status.cost}'

{"totalUSD": "4.182500", "heldUSD": "0.750000", "bySegment": {"bootUSD": "0.121000", "runningUSD": "3.980000", "teardownUSD": "0.081500"}}

heldUSD is reserved credit. Review the final total in the run’s Cost tab.

List and group usage

nodus get usage --since 2d
nodus get usage --group-by project,meter
nodus get usage --group-by member --since 30d
nodus get usage --group-by label:team,day
nodus get usage --group-by rank,segment --field-selector object.uid=<uid of a multi-node Job>

--group-by accepts project, kind, member, meter, day, segment, rank and label:<key>. member is the person who started the work, whichever of their API keys they used. Labels are the ones the object carried when it was admitted, so label your work before you submit it:

metadata:
  name: train-llama
  labels:
    team: research

Grouped totals always add up to the ungrouped total: every line lands in exactly one group, and lines without the grouped value share an empty group.

Export as CSV

nodus get usage --since 30d -o csv > usage.csv
curl -H "Authorization: Bearer $NODUS_TOKEN" -H "Accept: text/csv" \
  "https://api.nodus-compute.ai/v1/usagerecords?since=30d"

Amounts are in US dollars. Use the exported totals to reconcile your spending with the console.

For help with a charge, see Receipts and invoices.