Usage and spend (dsh-usage-spend)

Shows the session's token usage and an estimated spend under the DSH composer, priced at DeepSeek's peak and off-peak rates, and appends the amount to the built-in per-turn usage action. Currency and exchange rate are configured on the Plugins page.

What you get

• Composer usage pill: 85.3M tok · ≈¥3.09 · cache hit 99.4%, replacing the built-in usage row.
• Click the card: the header shows the exact token count and amount, followed by buckets for cache hits, uncached input, cache reads, cache writes, output and the billing window.
• Per-turn action: the built-in 用量 85.3M tok becomes 85.3M tok · ≈¥3.09, priced at that turn's end time.
• Peak pricing: Beijing time weekdays 09:00–12:00 and 14:00–18:00 cost double; everything else, weekends and public holidays included, is off-peak. The session total uses the windows that were in effect when the tokens were spent.
• Plugins page settings: currency (CNY / USD / both), exchange rate, and whether to show the sidebar balance, with a read-only price table below the form.
• Sidebar balance: 余额 ¥12.34 at the bottom of the sidebar, refreshed every 60 seconds or on click; the grant is in the tooltip; collapsed the sidebar shows a compact amount. A 峰 / 谷 / 混 badge after the amount describes this session's billing-window mix, and the tooltip spells it out. Can be turned off.

Install

dsh plugin --profile <profile> add dsh-usage-spend

Or in DSH Desktop / Web open Plugins → Add plugin, enter dsh-usage-spend, then choose Enable now. Restart or reload afterwards.

Open Plugins and expand the Usage and spend card to confirm the usage-cost row is on.

Settings

Click Configure on the row; changes apply immediately. They are written to the profile's cordis.patch.yml:

- id: usage-cost
  name: 'dsh-usage-spend'
  config:
    currency: CNY      # CNY | USD | BOTH
    usdToCny: 7.2
    showBalance: true

Turning the row off removes the pill, the per-turn amount and the sidebar balance; turning it back on restores them.

How the estimate works

Rates come from DeepSeek's official card (api-docs.deepseek.com/zh-cn/quick_start/pricing, checked 2026-11-07), in CNY per 1M tokens, and the table below is the off-peak rate:

Model	Input (cache miss)	Input (cache hit)	Output
deepseek-flash (DeepSeek-V4.1-Flash-1017)	1	0.02	4
deepseek-v4-pro (DeepSeek-V4-Pro-0813)	4.5	0.15	13.5

deepseek-v4-flash and deepseek-v4-flash-vision-exp are retired names that still work: requests are served by V4.1-Flash and billed at the Flash price, so they share its rates. deepseek-chat and deepseek-reasoner were discontinued on 2026-07-24 and are no longer priced.

Peak and off-peak

DeepSeek charges half the peak price off-peak, so peak = twice the table.

• Peak: Beijing time, Monday to Friday, 09:00–12:00 and 14:00–18:00
• Everything else is off-peak: nights, the lunch gap, weekends and whole public holidays
• Holidays follow the State Council schedule; the plugin ships the 2026 dates and needs one update a year

How the numbers are produced:

• Cost = (uncached input × input + cache reads × cache-read + cache writes × cache-write + output × output) / 1e6 × window multiplier
• Cache writes bill at the cache-miss input price, matching DeepSeek
• Per-turn amounts use that turn's end time, so they are exact
• The session total replays the session's own log hour by hour: the Host route reads the raw event log, files each event's four token counters (uncached input / cache reads / cache writes / output) into whole-hour buckets by its own timestamp, then prices every bucket at the multiplier that actually applied in that hour and sums them. Every peak boundary sits on a whole hour and Beijing is a whole 8 hours ahead of UTC, so bucketing never straddles a boundary. Reopening an old session still bills it at its original windows
• The blend is weighted by money, not by token count: a million output tokens and a million cache-read tokens differ by two hundred times in price, which a flat token share would get wrong
• The card's billing-window row and the sidebar badge report the peak share of this session's tokens: 谷 off-peak only, 峰 peak only, 混 when it spans both (with the percentage in the card / tooltip)
• When the log cannot be read (a session with no usage yet, or no session-query service), it falls back to the window in effect now and the badge reverts to the live 峰 / 谷
• The badge is hidden when the sidebar is collapsed or the balance chip is turned off; the card's billing-window row still shows it
• CNY is the base currency; USD is converted with the configured rate and only affects that column
• Discounts, granted credit, Search/Fetch fees and the platform's actual bill are not included. This is an estimate only.

Custom prices

Write localStorage["dsh.cost.prices"] from the browser console, keyed by model name (CNY per 1M tokens, off-peak; peak doubles it):

{
  "deepseek-flash": { "input": 1, "cacheRead": 0.02, "cacheWrite": 1, "output": 4 }
}

Keys may be the full model name, provider/model, or the bare model name. Reload to apply.

0.1.0 overrides were USD; 0.2.0 switched to CNY and added the peak multiplier, so old overrides need re-entering in the new unit. 0.2.2 prices the session total hour by hour from its log, falling back to the live window only when the log is unreadable.

Compatibility and limits

• Targets the client slot / projection API of DSH 0.2.2-rc.1.
• The per-turn text is rewritten through a DOM observer; if a DSH release changes the built-in button's structure it degrades to the original 用量 N tok and never affects the session.
• Switching models inside a session prices every hourly bucket at the current model's rate (historical models are not replayed), so the total remains an estimate.
• Billing windows come from the local Host route /api/dsh-usage-spend/window. It only reads and aggregates the session log by hour, never uploads the log and never calls a pricing API; the route is owner-only.
• The sidebar balance calls account.getBalance (DeepSeek account) and shows -- when signed out or when the read fails. It is the platform's balance, not a local estimate.
• Currency and rate come from host settings; when the settings service is unavailable it falls back to localStorage (dsh.cost.currency / dsh.cost.usdToCny).

License

MIT