dsh-deepseek-pricing
English · 简体中文
A DeepSeek Harness plugin that answers the two questions that decide a DeepSeek API bill: is the API on peak (full price) or off-peak (exactly half price) right now, and when does it flip. It also reports today's peak windows and the per-model prices for that tier from a bundled rate card transcribed from DeepSeek's pricing page on 2026-10-15 (data_metadata.pricing_checked_on). The built-in China public-holiday calendar covers 2026 only. Prices are not fetched at runtime.
Registering one tool:
| Tool | What it returns |
|---|
deepseek_pricing_tier | tier (peak/off), the canonical reason key (shared with the panel and its CLI), Beijing wall clock, today's peak windows, the next switch time + countdown, per-model prices from the bundled rate card (checked 2026-10-15; not a live fetch), data_metadata (pricing-check date + source + holiday-year coverage; holidays are 2026 only), calendar_coverage / current_calendar_covered / warnings, and — when days > 0 — the upcoming switches in the rolling window [at, at + days×24h) |
Install
dsh plugin --profile web add "github:ybbms777/dsh-deepseek-pricing"
The package declares dsh.bundle.patch, so dsh plugin activates it as a profile layer. Restart dsh --profile web afterwards, then check Settings → Plugins. Peer dependencies: @deepseek-ai/cordis (^4.0.1; both of the DSH lines below ship 4.0.5) and @deepseek-ai/dsh-tools (^0.0.1-rc.1 || ^0.2.0-rc.2). DSH 0.2 compares its own runtime version to each @deepseek-ai/dsh-* peer range with prerelease matching, and that range covers the 0.0.1-rc line and the 0.2.x line from 0.2.0-rc.2.
Why an agent wants this
Off-peak is exactly 50% of peak. DeepSeek's pricing page states the peak windows but does not say how a request that spans a tier boundary is assigned, so this plugin does not claim to know: treat the actual bill as the authority. What it does tell you is which tier an instant falls in:
peak hours are Beijing (UTC+8) Mon–Fri 09:00–12:00 and 14:00–18:00, excluding Chinese public holidays; everything else — weekday nights, the 12:00–14:00 lunch break, all weekend, all holidays — is half price.
So a job that can wait costs half as much. The tool is pure arithmetic on a bundled rate card transcribed from DeepSeek's pricing page on 2026-10-15, plus a China holiday calendar that covers 2026 only: no network calls, no API key, no credentials, isConcurrencySafe is true, and it never writes anything.
Use
Once mounted, the model calls deepseek_pricing_tier on its own. Typical args:
{ "at": "2026-10-12T09:30:00+08:00", "format": "summary" } // evaluate a specific instant
{ "days": 7, "format": "json" } // now + upcoming switches
Rendered output for a peak instant:
PEAK — DeepSeek bills full price right now
now (Beijing): 2026-10-12 09:30:00 (Monday) — outside the weekday peak windows (Beijing 09:00-12:00, 14:00-18:00)
today's peak windows: 09:00-12:00, 14:00-18:00 (Beijing)
next switch: 2026-10-12 12:00:00 → off-peak (half price) (in 0d 02:30:00)
pricing checked 2026-10-15 · holiday years 2026
deepseek-flash: in(cache miss) 2 / out 8 RMB per 1M — DeepSeek-V4.1-Flash, concurrency 2500
deepseek-v4-pro: in(cache miss) 9 / out 27 RMB per 1M — DeepSeek-V4-Pro（0813 版）, concurrency 500
One implementation, two consumers
The peak/off-peak rule is not re-implemented here. tier.js is generated by tools/sync-core.mjs from the /*CORE-START*/ … /*CORE-END*/ block of deepseek-pricing-panel's index.html, at a pinned commit, verbatim:
node tools/sync-core.mjs # regenerate tier.js
node tools/sync-core.mjs --check # CI: fail if tier.js drifted from the pin
The generated file carries the source commit and the CORE block's SHA-256, and tests/core.test.mjs asserts the header — so the model-facing tool and the human-facing HTML panel can never disagree about the rule.
Tests
npm ci
node --test
18 tests, no test framework beyond Node's own runner. tests/plugin.test.mjs boots the real harness packages: a real @deepseek-ai/cordis context with a real @deepseek-ai/dsh-tools tool registry (ToolRegistry on 0.0.1-rc.1, ToolRuntime from 0.0.1-rc.5), mounts the plugin with ctx.plugin(), and executes the tool through the registry pipeline — asserting the model-facing schema, the rendered summary, the JSON value, the error path for an unusable at, and the prompt-section wiring. The only stand-in is the systemPrompt service the registry injects (a two-method stub). CI runs the suite on Ubuntu + Windows × Node 20/22 × dsh-tools 0.0.1-rc.5 and 0.2.0-rc.2 (both with cordis 4.0.5), plus the drift check.
Model names
deepseek-flash is DeepSeek-V4.1-Flash, not V4-Flash: the legacy ids deepseek-v4-flash / deepseek-v4-flash-vision-exp still resolve, but those models are retired and requests are served by V4.1-Flash at Flash prices. deepseek-v4-pro is DeepSeek-V4-Pro. Both ids and versions were checked on 2026-10-10 (data_metadata.model_mapping_checked_on) against GET https://api.deepseek.com/models. The plugin does not call that endpoint at runtime.
Caveats
- Prices are a bundled rate card transcribed from DeepSeek's pricing page on 2026-10-15. They are not fetched live. If the published prices change, the card stays stale until the panel pin is regenerated.
- A government make-up workday (调休上班日) is off-peak under the rule, because DeepSeek distinguishes only Mon–Fri from weekend.
- The built-in China holiday calendar covers 2026 only. A later year is estimated from the weekday rule and reported as uncovered (
calendar_coverage / warnings) until HOLIDAYS is updated upstream and this package is re-pinned with tools/sync-core.mjs.
License
MIT.
简体中文
这是一个 DeepSeek Harness 插件，回答决定 DeepSeek API 账单的两个问题：现在按高峰（全价）还是空闲（正好半价）计费、下一次切换在几点，并给出今天的高峰窗口。各模型单价来自内置价目表，于 2026-10-15 从 DeepSeek 定价页 誊录（即 data_metadata.pricing_checked_on），运行时不联网刷新。内置的中国法定节假日日历只覆盖 2026 年。
注册的工具：deepseek_pricing_tier —— 返回 tier（peak/off）、判定原因、北京时间、今天的高峰窗口、下次切换时刻与倒计时、内置价目表中该档位的各模型单价（核对日期 2026-10-15，不是实时拉取；节假日只覆盖 2026 年），可选未来若干天的切换列表。
安装：
dsh plugin --profile web add "github:ybbms777/dsh-deepseek-pricing"
包内声明了 dsh.bundle.patch，dsh plugin 会把它作为 profile 层启用；重启 dsh --profile web 后在「设置 → 插件」中查看。Peer：@deepseek-ai/cordis ^4.0.1（这两条 DSH 线都带 4.0.5），@deepseek-ai/dsh-tools ^0.0.1-rc.1 || ^0.2.0-rc.2（覆盖 0.0.1-rc 与从 0.2.0-rc.2 起的 0.2.x，当前 DSH 安装时不需要 allow-version）。
为什么 Agent 需要它：空闲价正好是高峰的 50%，只取决于请求什么时候跑完。高峰 = 北京时间（UTC+8）周一至周五 09:00–12:00、14:00–18:00（不含中国法定节假日）；其余全部时段 —— 工作日夜里、午休、整个周末、整个节假日 —— 都是半价。所以能等的批处理任务，成本直接减半。单价是 2026-10-15 誊录的内置价目表，节假日数据只覆盖 2026 年。纯本地算术：不联网、不需要 API key、不写任何文件。
一份实现，两个消费者：峰谷规则没有在这里重写。tier.js 由 tools/sync-core.mjs 从 deepseek-pricing-panel 的 index.html 里 /*CORE-START*/ … /*CORE-END*/ 段按固定 commit 原样生成，文件头记录来源 commit 与 CORE 段的 SHA-256，node tools/sync-core.mjs --check 在 CI 里守住不漂移 —— 因此面向模型的工具与面向人的 HTML 面板不可能对规则产生分歧。
测试：npm ci && node --test，18 个用例、只用 Node 自带 runner。其中 tests/plugin.test.mjs 会真的启动 harness 包（真实的 @deepseek-ai/cordis 上下文 + 真实的 dsh-tools ToolRegistry），用 ctx.plugin() 挂载插件并走注册中心管线执行工具。
注意：deepseek-flash 是 DeepSeek-V4.1-Flash（不是 V4-Flash，旧模型名已下线但由 V4.1-Flash 承接；模型 id 于 2026-10-10 对照过 GET https://api.deepseek.com/models，插件运行时不请求该接口）。调休上班日按规则算空闲半价。单价是 2026-10-15 从官方定价页誊录的内置价目表，不是实时拉取；节假日日历只覆盖 2026 年，新年安排需要在上游面板更新 HOLIDAYS 后重新 pin。
