[Docs] Explain DeepSeek V4 Pro provider versions - #27
Draft
zoomote[bot] wants to merge 3 commits into
Draft
Conversation
Author
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 to the first-party 0813 checkpoint.Why this change was made
The 0813 update changed the checkpoint behind DeepSeek's existing API alias rather than introducing a new model ID or new open weights. The provider guide needs to preserve that distinction so users do not assume every V4 Pro host serves the same checkpoint.
Impact
Users can choose a DeepSeek V4 Pro route with accurate expectations about the checkpoint, provider ID, and pricing stability.
Related PRs
Screenshots