Skip to content

fix(opencode): update test fixture DeepSeek pricing to match official rates - #31151

Closed
licat2023 wants to merge 3 commits into
anomalyco:devfrom
licat2023:fix/models-dev-deepseek-pricing
Closed

fix(opencode): update test fixture DeepSeek pricing to match official rates#31151
licat2023 wants to merge 3 commits into
anomalyco:devfrom
licat2023:fix/models-dev-deepseek-pricing

Conversation

@licat2023

@licat2023 licat2023 commented Jun 6, 2026

Copy link
Copy Markdown

Issue for this PR

Closes #31150

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Updates the test fixture (\models-api.json) to correct the DeepSeek model pricing that was stale/outdated. The models.dev API currently serves incorrect pricing for DeepSeek V4 models, and this fixture snapshot had the same stale data.

Changes:

Model Field Old New
deepseek-v4-pro input 1.74 0.435
deepseek-v4-pro output 3.48 0.87
deepseek-v4-pro cache_read 0.145 0.003625
deepseek-v4-flash cache_read 0.028 0.0028
deepseek-chat cache_read 0.028 0.0028

These values match DeepSeek's official pricing page:

  • V4 Flash: input .14, output .28, cache hit .0028
  • V4 Pro: input .435, output .87, cache hit .003625

The models.dev source TOML files for V4 models already have correct pricing. This fixture just needed to catch up. A companion PR at anomalyco/models.dev#2037 fixes the remaining deprecated aliases.

How did you verify your code works?

  1. Compared all values against DeepSeek's official pricing page (https://api-docs.deepseek.com/quick_start/pricing) - every change matches the published rates
  2. Compared against the models.dev source TOML files at anomalyco/models.dev which already contain the correct values
  3. Ran \grep\ across the fixture to confirm no other instances of the stale DeepSeek V4 pricing (1.74/3.48/0.145) remain in the deepseek provider section

Screenshots / recordings

N/A - test fixture data change only.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

… rates

Updated models-api.json test fixture for DeepSeek models:
- deepseek-v4-pro: input 1.74->0.435, output 3.48->0.87, cache_read 0.145->0.003625
- deepseek-v4-flash: cache_read 0.028->0.0028
- deepseek-chat: cache_read 0.028->0.0028

These match DeepSeek official pricing at https://api-docs.deepseek.com/quick_start/pricing
@github-actions

github-actions Bot commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

@github-actions github-actions Bot added needs:compliance This means the issue will auto-close after 2 hours. and removed needs:compliance This means the issue will auto-close after 2 hours. needs:issue labels Jun 6, 2026
@github-actions

github-actions Bot commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

Thanks for updating your PR! It now meets our contributing guidelines. 👍

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: models.dev serving stale DeepSeek V4 pricing (4x-40x wrong for pro)

1 participant