This repository was archived by the owner on Oct 16, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 16, 2026. It is now read-only.
feat: compute costUsd from token usage via model pricing table #635
Description
Status Update (2026-04-05)
This issue remains a good core capability issue.
The Studio-specific dashboard ambitions are no longer urgent. If this work is done, the important part is still the underlying cost computation so cost data is present in result artifacts and available to any consumer (CLI, CI, Studio, or external tooling).
Revised Scope
In scope
- pricing table for models that do not report cost directly
- cost computation from token usage
- clear precedence for provider-reported
costUsd - user overrides/extensions for pricing data
Deprioritized
- large Studio cost-attribution dashboard work
- budget-control / optimization-center UI in Studio
- making Studio the primary consumer of this feature
Acceptance Signals
-
costUsdis computed when token usage exists and provider cost is absent - provider-reported cost is never overridden
- unknown models remain
undefinedrather than guessed - cost data is available in result artifacts for downstream consumers
Activity
christso commentedon Mar 27, 2026
Extension: Cost Attribution Views in Dashboard
This issue currently defines the core cost computation engine. The following dashboard surface should be added:
Dashboard capabilities for cost analytics
How this connects
Research source