feat: add priority_pricing#1160
Merged
Merged
Conversation
LordGameleo
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Schema-only, optional field with no behavior changes in this diff; downstream cost calculation must explicitly use it to affect billing.
Overview
Adds an optional
priority_pricingblock on eachCostWithRegionentry so model YAML can declare a separate#Costprofile (same fields as standard pricing) alongside the existing regional#Costfields.The Cue schema in
model.cueis the source of truth;types.tspicks up the same optionalpriority_pricing?: CostonCostWithRegionvia the existing OpenAPI/typegen pipeline.Reviewed by Cursor Bugbot for commit fe8d146. Bugbot is set up for automated code reviews on this repo. Configure here.