Track exactly what every request costs and export your usage.
Every request Omnia serves writes a ledger entry with its model, token
counts, and cost. Nothing is estimated; the ledger is the exact record of what
you spent, down to the micro-cent (1,000,000 micros = $1.00).
Unique id for the request (also the settlement key).
Model
The model id served.
Prompt tokens
Input tokens.
Completion tokens
Output tokens (includes partial output on a cancelled stream).
Total tokens
Prompt + completion.
Cost
The amount deducted, to the micro-cent.
Status
success, or error for a request that failed or was partial.
Per-request costs are often a small fraction of a cent. The ledger stores full
micro-cent precision, so you see the real charge rather than a rounded $0.00.
Export your full usage ledger as CSV from the Usage page: one row per
request, with time, request id, model, prompt/completion/total tokens, cost,
and status. Use it for your own accounting, reconciliation, or per-model cost
analysis.
Costs on the ledger are computed from the tokens used and the model’s rates. If
a model is priced at, say, 0.50permillioninputtokens∗∗and∗∗1.50 per
million output tokens (illustrative), a request with 1,200 prompt tokens and
300 completion tokens is charged:
The Usage page is your billing record: money spent, to the micro-cent.
For performance metrics such as latency, throughput, error rates, and
per-model breakdowns, see Observability. The two are
separate: observability does not affect what you’re billed.