Repository navigation
Conversation
Refs simonw#70. DeepSeek moved V4 Flash and V4 Pro to two-tier time-of-day pricing effective 2026-08-17; every number in this file predates that. Old prices get to_date 2026-08-17 rather than being overwritten, so historical-v1.json keeps them. Peak rates go in as separate ids, following the existing -200k convention for models that carry two price points. Source: https://api-docs.deepseek.com/quick_start/pricing/ read 2026-08-22.
Author
|
Pushed one more commit: DeepSeek shipped
One thing the schema can't hold, flagged rather than folded in: images bill at up to 384 tokens each, so for image input these per-token figures are the multiplier, not the price. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #70 — the numbers side of it, ready to merge or to throw away if you'd rather shape it differently.
Every DeepSeek V4 figure on the site predates the 2026-08-17 repricing. Source for the new ones: https://api-docs.deepseek.com/quick_start/pricing/, read 2026-08-22.
deepseek-v4-flashdeepseek-v4-flash-peakdeepseek-v4-prodeepseek-v4-pro-peakPeak is 01:00–04:00 and 06:00–10:00 UTC; everything else off-peak.
What this PR chooses, of the three options in #70: option 2, separate ids, because it reuses the
-200kpattern the dataset already has and puts the 2x on the page instead of in a footnote. If you'd rather have option 1 (one row, multiplier in the name) or option 3 (a real time-window field), close this and I'll rewrite it — the figures above are what matters and they're the same either way.Old prices get
to_date: "2026-08-17"instead of being overwritten, sohistorical-v1.jsonkeeps the pre-repricing record.python3 scripts/build.pyruns clean and the DeepSeek block ofcurrent-v1.jsoncomes out as the table above.One thing these ids still can't express, flagged rather than hidden: from midnight Beijing time on 2026-08-23, DeepSeek bills Saturdays and Sundays at off-peak rates around the clock.
from_date/to_dateare calendar dates, so there's no day-of-week dimension either. The-peakrows are therefore an upper bound that's correct on weekdays and 2x too high at weekends. If that bothers you, option 1 collapses the problem into prose and might be the better trade after all.I left
deepseek-chatanddeepseek-reasoneralone. They're gone from DeepSeek's pricing page entirely, so I have nothing live to quote for them — noted in #70 as possibleto_datecandidates rather than something to fill in.