Model Cost Calculation
The Cost Management page shows estimates, not invoices. This page explains how it counts days and which calls it includes in your spend.
How Days Are Counted
The Cost Management page counts every day in the date range as a UTC day, the same way providers bill. When you pick a day, the page shows the spend from 00:00 to 24:00 UTC of that day, even if your browser is in another timezone. For example, if you pick October 16 in Berlin, you see the spend of October 16 UTC, not of October 16 in Berlin time.
This means the total for a day matches the same day in your provider's console or invoice, and matches the cost exports. To reconcile spend with a provider, compare the same UTC day on both sides. The daily spend chart places each bar on its UTC day, and the Projected this month figure is also calculated from UTC days.
Pipeline Debug Runs
If your spend includes testing, note that the model calls of pipeline debug runs, such as runs you start from Builder, are billed by the provider, so the Cost Management page counts them too. They appear as query usage, the same as other queries. If the run uses a saved pipeline, the page groups the usage under that pipeline; a run of an unsaved pipeline configuration isn't linked to a pipeline. A failed debug run counts because its calls were billed. A run that stops at a breakpoint counts the calls made so far, and resuming adds only the calls made after the breakpoint, so no call is counted twice.
Durable Runs
Token usage of durable runs is recorded when a run finishes. Tokens of an earlier attempt that was lost together with its host aren't recorded. For details, see Token Usage of Durable Runs.
Related Information
Was this page helpful?