Skip to main content
For the complete documentation index for agents and LLMs, see llms.txt.

View Cost and Quality Trends on the AI Operator PageBeta

Beta
This is coming — this page describes a feature that's still being rolled out and may not be available to you yet.

To find out whether a release changed what a Service costs and how well it answers, use the Cost over time card on the Service's AI Operator page. It shows daily cost next to the published revisions and the measured quality of each evaluation run.

About This Task​

You see the Cost over time card only if you have permission to read costs.

Chart Elements​

The card includes:

  • Cost per day: a line showing the Service's total cost for each day in the selected period. This is the Service's total spend, so it also rises and falls with traffic, not only with configuration changes.
  • Version markers: a dashed vertical line for each published revision that served traffic, labeled with its version. Revisions that failed to deploy are left out, so every marker reflects a release your users could reach.
  • Quality (average score) dots: a dot for each evaluation run, plotted on a second axis from 0 to 1. Each dot is the run's baseline quality, calculated as the mean of its scored metrics. Label metrics and evaluations that haven't finished are skipped, so a dot always reflects a completed, scored run.
  • Date range selector: switch between 30 days, 90 days, and 6 months to widen or narrow the window shown in the chart.

If the Service has no recorded cost for the selected period, the card shows a message that no cost was recorded. If the cost data can't be loaded, the card shows a message asking you to refresh and try again.

Read the Chart​

  1. Open the Service and go to its AI Operator page.
  2. Find the Cost over time card.
  3. Select a date range: 30 days, 90 days, or 6 months, depending on how far back you want to look.
  4. Compare the cost line against the dashed version markers to see whether a cost change lines up with a specific release.
  5. Compare the quality dots near a version marker to see whether that release changed answer quality, not just cost. Because cost also moves with traffic, use the markers and dots together to judge whether a release caused a cost change.