[codex] Support DeepSeek V4 Pro, Grok 4.6, and tiered pricing - #176
Closed
LeenHawk wants to merge 1 commit into
Closed
[codex] Support DeepSeek V4 Pro, Grok 4.6, and tiered pricing#176LeenHawk wants to merge 1 commit into
LeenHawk wants to merge 1 commit into
Conversation
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
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.
What changed
reasoning_effortand raise its documented output limit to 384KWhy
Grok 4.6 uses higher token prices after 200K prompt tokens, but this behavior is not xAI-specific. OpenAI, Google, Qwen, Seed, and other model families use different thresholds and sometimes multiple tiers. A generic tier representation avoids hard-coded model multipliers and keeps billing aligned with current provider catalogs.
Impact
Existing price rules continue to use their base rates. Rules may optionally provide
pricing_tiers_json; the highest matching prompt-token threshold overrides only the rate categories it declares. Old SQLite/libSQL schemas are repaired automatically, and migration coverage verifies tier JSON can be written and read after upgrade.Validation
cargo check --all-targets --all-featurescargo fmt --all -- --checkgit diff --check