Repository navigation
[FEATURE]: Add markup disclosure column to Go pricing table — V4 Flash parity vs V4 Pro 4x markup is invisible to users #32116
Description
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
The Go pricing table at https://opencode.ai/docs/go/ displays per-token costs uniformly, but the markup model is inconsistent:
- V4 Flash: $0.14/$0.28 — at parity with official DeepSeek ($0.14/$0.28)
- V4 Pro: $1.74/$3.48 — 4x markup vs official DeepSeek ($0.435/$0.87)
Both sit in the same table with identical formatting. V4 Flash at exact parity creates a false baseline — users have no reason to suspect V4 Pro carries a 300% service fee. The only way to discover this is to cross-reference DeepSeek's official pricing.
The problem is reinforced by the request estimates: the "1,350 req/5h" for V4 Pro is calculated against the 4x inflated per-token price. At actual DeepSeek rates ($0.435/$0.87), that same $12/5h limit would yield ~5,400 requests. The estimates silently penalize V4 Pro users.
Request: Add a disclosure column to the pricing table showing markup vs official provider pricing, e.g.:
| Model | Input | Output | Cached Read | vs Official |
|---|---|---|---|---|
| V4 Flash | $0.14 | $0.28 | $0.0028 | Parity |
| V4 Pro | $1.74 | $3.48 | $0.0145 | 4x markup |
This isn't asking for a price cut — it's asking for transparency so users can make informed decisions about which models to use through Go vs bringing their own key.
Activity
github-actions commentedon Jun 12, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:, include the verification checkbox, and describe the problem/need).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.
[-]Go pricing table: add markup disclosure column — V4 Flash at parity vs V4 Pro 4x markup is invisible to users[/-][+][FEATURE]: Add markup disclosure column to Go pricing table — V4 Flash parity vs V4 Pro 4x markup is invisible to users[/+]github-actions commentedon Jun 12, 2026
Thanks for updating the issue! It now follows the feature request template correctly — the verification checkbox is checked, the title starts with
[FEATURE]:, and the description clearly explains the problem and the requested change. Theneeds:compliancelabel has been removed.marlonwq commentedon Jun 12, 2026
Strongly support this. The discrepancy between V4 Flash (exact parity) and V4 Pro (4x markup) without visual indication is misleading, even if unintentional. It creates a false baseline for users.
If adding a full column to the table causes responsive design or UI clutter concerns, an alternative could be adding a dynamic "Pricing Note" or tooltip next to the model names (e.g.,
V4 Pro (Includes service markup)), or a simple breakdown toggle/footnote.Transparency here is key, especially since the request estimates silently penalize V4 Pro users who might otherwise prefer to bring their own API key.
mstephano commentedon Jun 18, 2026
The deepseek V4 flash model is also much less expensive now on competitor OpenRouter at $0.09/$0.18, so we could potentially have more requests per month at that price matching (if that can be done) and have a possibility to attract more customers to OpenCode GO.
github-actions commentedon Aug 18, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.