You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenCode Go: DeepSeek V4 Pro pricing doesn't match official DeepSeek pricing (4x markup vs V4 Flash at parity) #31504
DeepSeek V4 Flash — exact match across all tiers (Input, Output, Cached Read).
DeepSeek V4 Pro — 4x markup across all tiers:
Input: $1.74 vs $0.435 (4x)
Output: $3.48 vs $0.87 (4x)
Cached Read: $0.0145 vs $0.003625 (4x)
Request Limits
If the $10/month Go subscription is intended to reflect pass-through pricing, the request limits for V4 Pro (3,450 per 5 hours) are lower than what subscribers would expect at true DeepSeek rates. Since the per-token prices in the docs are inflated 4x for V4 Pro only, the calculated request cap is also lower than it should be.
Expected
Either match V4 Pro pricing to DeepSeek official like V4 Flash, or document the markup
If per-token pricing were corrected, V4 Pro request limits should scale up accordingly
No issue template was used. Please resubmit using one of the three required templates: Bug Report, Feature Request, or Question. This appears to be a bug report, so the Bug Report template would be appropriate.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Activity
github-actions commentedon Jun 9, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Jun 9, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.