Skip to content

OpenCode Go: DeepSeek V4 Pro pricing doesn't match official DeepSeek pricing (4x markup vs V4 Flash at parity) #31504

Closed as not planned

Description

Pricing Discrepancy

DeepSeek Official Pricing (per 1M tokens)

From https://api-docs.deepseek.com/quick_start/pricing:

Model Cache Hit Cache Miss (Input) Output
V4 Pro $0.003625 $0.435 $0.87
V4 Flash $0.0028 $0.14 $0.28

OpenCode Go Pricing (per 1M tokens)

From https://opencode.ai/docs/go/ (Usage Limits section):

Model Input Output Cached Read
V4 Pro $1.74 $3.48 $0.0145
V4 Flash $0.14 $0.28 $0.0028

Comparison

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

Activity

  1. github-actions commented on Jun 9, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • 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:

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. github-actions commented on Jun 9, 2026

    @github-actions
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions