[Improve] Align DeepSeek V4 Pro provider metadata - #1237
Draft
zoomote[bot] wants to merge 2 commits into
Draft
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
Author
|
Addressed in |
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
deepseek-v4-proalias as DeepSeek V4 Pro 0813 only for the first-party DeepSeek API and OpenCode Go proxy route.deepseek-ai/DeepSeek-V4-Propreview-weight model without applying the 0813 checkpoint label, and leaves Fireworks AI on its existing preview-weight metadata.$0.435input,$0.87output, and$0.003625cache reads, and omits an unverified Baseten cache-write price.Why this change was made
DeepSeek swapped the checkpoint behind its existing
deepseek-v4-proAPI alias to 0813 without introducing a new model ID. OpenCode Go proxies that first-party route, while Fireworks AI and Baseten self-host the previously published V4 Pro preview weights, so their labels must remain undated.Impact
Users see accurate version labels and cost/capability metadata for each route without a fabricated dated model ID. DeepSeek warns that it plans a significant overall price increase, so these hardcoded rates may need a follow-up update.
Related PRs
Screenshots