You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Per-registry price overrides for cost (models.dev default) #505
changed the title [-]Per-client price overrides for cost (models.dev default)[/-][+]Per-registry price overrides for cost (models.dev default)[/+]on Aug 22, 2026
OpenAI public docs: list prices and Scale/Reserved capacity are per model. Committed/Guaranteed Capacity language is often a portfolio % discount off list, not a published absolute rate sheet. Procurement deals may use either absolute $/model rates or a blanket multiplier.
v1 still: registry pricing_overrides per model slug (input/output USD/token). Nice-to-have: optional registry-level multiplier (e.g. 0.8 = 20% off models.dev) applied when no absolute override matches. Precedence: absolute override → multiplier → models.dev.
This is required to estimate real monthly cost, not just decorate events.
Without registry overrides, monthly rollups use models.dev list prices and diverge from the customer’s actual invoice / enterprise rates. With overrides (absolute per-model and/or optional flat multiplier), TrustGate can sum usage × resolved_price over the month and produce a credible cost estimate.
Extra acceptance
Monthly / period cost aggregation uses the same resolved prices as per-request Cost (override → multiplier → models.dev)
Docs call out that accurate monthly estimates depend on configuring registry pricing to match the contract
Activity
[-]Per-client price overrides for cost (models.dev default)[/-][+]Per-registry price overrides for cost (models.dev default)[/+]vgmartinez commentedon Aug 22, 2026
Clarification (enterprise contract shapes)
OpenAI public docs: list prices and Scale/Reserved capacity are per model. Committed/Guaranteed Capacity language is often a portfolio % discount off list, not a published absolute rate sheet. Procurement deals may use either absolute $/model rates or a blanket multiplier.
v1 still: registry
pricing_overridesper model slug (input/output USD/token).Nice-to-have: optional registry-level multiplier (e.g.
0.8= 20% off models.dev) applied when no absolute override matches. Precedence: absolute override → multiplier → models.dev.vgmartinez commentedon Aug 22, 2026
Product intent (Victor)
This is required to estimate real monthly cost, not just decorate events.
Without registry overrides, monthly rollups use models.dev list prices and diverge from the customer’s actual invoice / enterprise rates. With overrides (absolute per-model and/or optional flat multiplier), TrustGate can sum
usage × resolved_priceover the month and produce a credible cost estimate.Extra acceptance
Cost(override → multiplier → models.dev)Merge pull request #515 from NeuralTrust/cursor/registry-pricing-over…