Skip to content

[Docs] Explain DeepSeek V4 Pro provider versions - #27

Draft
zoomote[bot] wants to merge 3 commits into
mainfrom
feature/deepseek-v4-pro-0813-3ma59xuwmw1at
Draft

[Docs] Explain DeepSeek V4 Pro provider versions#27
zoomote[bot] wants to merge 3 commits into
mainfrom
feature/deepseek-v4-pro-0813-3ma59xuwmw1at

Conversation

@zoomote

@zoomote zoomote Bot commented Aug 12, 2026

Copy link
Copy Markdown

​Opened on behalf of @taltas. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

  • Explains that DeepSeek and OpenCode Go route the stable deepseek-v4-pro alias to the first-party 0813 checkpoint.
  • Identifies Fireworks AI and Baseten as serving the published V4 Pro preview weights through their own inference infrastructure.
  • Lists each provider's exact model ID and version served in one table.
  • Notes DeepSeek's warning that it plans a significant overall price increase, so hardcoded rates may need follow-up.

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

DeepSeek provider routes and versions

DeepSeek planned pricing increase warning

@zoomote

zoomote Bot commented Aug 13, 2026

Copy link
Copy Markdown
Author

Addressed in ab2d4f4 and 1aead6b: the guide now distinguishes first-party 0813 routes from self-hosted preview weights, lists exact provider IDs/versions, and warns about DeepSeek's planned significant price increase. The draft PR metadata and screenshots were refreshed to the final rendered state.

@zoomote zoomote Bot changed the title [Docs] Document DeepSeek V4 Pro 0813 providers [Docs] Explain DeepSeek V4 Pro provider versions Aug 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant