anomalyco / anomalyco/models.dev

[Feat] Support time-based (peak/off-peak) pricing for DeepSeek V4 Pro and Flash

Open
#5,218 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6.9k
Forks
1.7k
Avg merge
3h 21m
Merged PRs (30d)
873

Description

Problem

DeepSeek switched to peak/off-peak billing on 2026-08-16. Prices now depend on the time of day, but models.dev only stores a single flat [cost] block per model, so the current entries are stale and there is no way to represent the real pricing.

Peak hours: 01:00–04:00 UTC and 06:00–10:00 UTC (7 h/day). All other hours are off-peak (half price).

New pricing (USD per 1M tokens)

DeepSeek V4 Pro

input output
off-peak $0.66 $1.98
peak $1.32 $3.96

DeepSeek V4 Flash

input output
off-peak $0.22 $0.66
peak $0.44 $1.32

(Reasoning tokens are billed at the output rate; cache read/write rates also vary by peak/off-peak.)

Current (stale) repo state
  • deepseek-v4-pro.toml: input 0.435 / output 0.87 / reasoning 0.87 / cache_read 0.003625
  • deepseek-v4-flash.toml: input 0.14 / output 0.28 / reasoning 0.28 / cache_read 0.0028
References

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating how the flat [cost] block is represented and how deepseek-v4-pro.toml and deepseek-v4-flash.toml are loaded. Check the DeepSeek pricing reference for peak and off-peak rates, then update the model data so both periods and cache rates are representable and the two stale entries use the new prices.

Written by the indexing model from the issue text.

Assessment

Domain
ai, data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.