dsh-meter English | 中文 DeepSeek bills by time of day now. This is the meter for it. Two peak windows a day, off-peak at half the peak rate. Cost stopped being a number you read afterwards and became a rate you are standing in. One line under the composer: what this session cost, which tariff is running, how long until it flips. Hover it for the tariff clock, the cache economics, and your balance.

Install

dsh plugin --profile web add @dshworks/dsh-meter
dsh --profile web

dsh plugin forwards to pnpm, so pnpm must be on PATH. Nothing else to configure: the meter appears under the composer as soon as a session bills its first request.

The line

2 turns · 2 steps | LLM 3.1s | TTFT avg 1.3s · 41 tok/s | Cache hit 50% | Input 44.3K tok
                    ¥0.0672  |  peak  |  off-peak in 48m

The harness's own stats line, untouched, and ours under it. This plugin adds a line — it does not shadow the shipped one, which is what a cost plugin has to do to append to it.

Hover or focus for the card. Inside a peak window the tariff is called out in amber and the countdown runs to the next off-peak hour:

Proof

Live-verified against dsh 0.1.0-rc.6 on 2026-08-15, in a real web session on DeepSeek-V4-Pro — not a mock:

Two currencies, no conversion

DeepSeek publishes two independent rate cards — USD for the international platform, CNY for the mainland one. An account is billed against exactly one of them, and neither table is a conversion of the other, so a plugin that picks with an exchange rate is wrong twice.

dsh-meter computes both and lets the account decide. GET /user/balance returns the currency the account is denominated in — a live account lists both rows with only one funded — so the meter reads the funded row and shows that side. Nothing to configure, nothing to guess from your interface language.

The balance request runs on the host, keyed by the same credential seam the LLM adapter uses; the browser gets parsed numbers over GET /dsh-meter/balance and never the key. It fires when the meter mounts and when you open the card, not on a schedule — set balance: false to turn the whole thing off and the meter keeps working.

The rate card

Carried verbatim in lib/core.js, per 1M tokens.

Peak is 01:00–04:00 and 06:00–10:00 UTC (09:00–12:00 and 14:00–18:00 Beijing). Every other hour is off-peak, including the two-hour gap between the windows. Off-peak is exactly half of peak — and still above the flat rate it replaced, by about 2.4x on output.

Source: https://api-docs.deepseek.com/quick_start/pricing, fetched 2026-08-13.

How the money is counted

Model Experience

None. dsh-meter adds no tool, no system-prompt section, no message, and no model call; it does not touch the request. Cost belongs to the person paying, not to the agent's context window.

KV Cache effect

None — the plugin never participates in a request.

Configuration

Everything below is a validated config field, set in your profile's cordis.patch.yml:

- id: dsh-meter
  config:
    currency: cny        # pin a rate card instead of detecting it
    balance: false       # never call /user/balance

Development

pnpm install
pnpm test                        # bundle-sync check, then vitest
node scripts/build-client.mjs    # regenerate lib/client.js after editing core/ui

lib/core.js holds the rate card, the tariff clock, and the fold. lib/balance.js is the account reader. src/ui.js is the browser surface. scripts/build-client.mjs inlines core + ui into lib/client.js, the bundle the harness serves — so the price table exists in exactly one file, and pnpm test fails if the generated bundle drifts from it.

Known limitations

• It is an estimate, not the invoice. List prices times reported tokens. Promotional pricing and any relay in front of the API are invisible to it.
• Tariff is inferred from the dispatch timestamp, which is the harness's clock. A request DeepSeek receives on the far side of a boundary can bill differently by a second or two.
• Non-DeepSeek routes are not priced. Their tokens are counted and their model named; the card reports them as unpriced instead of quietly applying DeepSeek's rates to someone else's API.
• The rate card is compiled in. DeepSeek changes prices; this plugin ships a snapshot taken 2026-08-13 and needs a release to follow one.
• Web only. The projection is available to any surface, but the readout is built for the Web UI. There is no TUI line.

Prior art

The dsh registry lists ~50 cost and usage plugins; several arrived the same week DeepSeek dated the switchover, and reading them shaped this one. The cache-savings framing comes from deepseek-cli's local usage ledger.

License

MIT