Skip to content

feat(pricing): the repricing is dated — encode the switch, a /pricing/ page, a pricing command - #21

Merged
lroolle merged 1 commit into
mainfrom
feat/pricing-page
Aug 13, 2026
Merged

feat(pricing): the repricing is dated — encode the switch, a /pricing/ page, a pricing command#21
lroolle merged 1 commit into
mainfrom
feat/pricing-page

Conversation

@lroolle

@lroolle lroolle commented Aug 13, 2026

Copy link
Copy Markdown
Member

Summary

DeepSeek dated its repricing on 2026-08-13: peak/off-peak billing on a new, higher card from 2026-08-16 16:00 UTC, peak hours 01:00-04:00 and 06:00-10:00 UTC (boundaries defined in UTC) at twice the off-peak rate. That flips the TASTE.md rejection of 2026-08-05 exactly as its expiry clause prescribed: the multiplier goes in, gated on the effective instant, never applied before it.

One schedule, four readers:

  • internal/deepseek: PriceAt / CostAt / PeriodAt / NextChange switch cards on the instant; estimates and ds models follow automatically. Tests pin the flip boundary, the UTC end-exclusive windows, and the next-change arithmetic at fixed instants.
  • deepseek pricing (new command): the billing period right now with local, UTC and Beijing time, when it changes, and both cards — computed locally from the same schedule the estimates use, no network, nothing spent. --json for scripts.
  • gateway meter: the same switch, plus Estimate reserves against the highest card an in-flight request could touch within the hour, so admission control cannot under-reserve across a boundary.
  • site: a dedicated /pricing/ page wired into nav, sitemap, llms.txt and the 404, carrying the dated schedule, both rate cards, and a "right now" strip. The strip is data-driven: build.py renders one schedule list as the visible table, the no-JavaScript verdict, and the JSON that pricing.js reads; pricing.test.js pins the period arithmetic against the committed HTML and the upstream ground truth, and runs in make site-check and CI.

Consistency guards: the embedded docs corpus is refreshed to the 2026-08-13 upstream (pricing, updates, V4-Pro GA news), so ds docs show quick_start/pricing, the site and the estimates trace to one source; make price-check still passes with the four rate-card literals mirrored between the CLI and the gateway. News page gets the dated-repricing entry, and the two undated announcements (2026-08-06 rise, 2026-06-29 peak policy) are resolved and point at it. Site copy stays em-dash-free.

Test plan

  • make check (fmt, vet, go tests, corpus-check, price-check, build, gateway, site-check incl. node site/pricing.test.js) — all green locally
  • deepseek pricing / deepseek pricing --json smoke-tested; flat card shown today, flip announced with countdown
  • generated HTML verified em-dash-free; page carries every number of both cards

Made with Cursor

…/ page, a pricing command

DeepSeek dated it on 2026-08-13: peak/off-peak billing on a new, higher
card from 2026-08-16 16:00 UTC, peak hours 01:00-04:00 and 06:00-10:00
UTC at twice the off-peak rate. This flips the TASTE.md rejection of
2026-08-05 exactly as its expiry clause prescribed: the multiplier goes
in, gated on the effective instant, never applied before it.

One schedule, four readers:

- internal/deepseek: PriceAt/CostAt/PeriodAt/NextChange switch cards on
  the instant; estimates and `ds models` follow automatically.
- `deepseek pricing`: the period right now (local, UTC, Beijing), when
  it changes, and both cards — computed locally, nothing spent.
- gateway meter: same switch, and Estimate reserves against the highest
  card an in-flight request could touch within the hour.
- site: a /pricing/ page carrying the dated schedule, both cards, and a
  "right now" strip driven by the same JSON the page embeds;
  pricing.test.js pins the boundary arithmetic and the ground truth.

The embedded docs corpus is refreshed to the 2026-08-13 upstream
(pricing, updates, V4-Pro GA news) so `ds docs show quick_start/pricing`
and the site cannot disagree. News page: the dated-repricing entry, the
two undated announcements resolved and pointing at it.

Co-authored-by: Cursor <cursoragent@cursor.com>
@lroolle
lroolle merged commit 64f461e into main Aug 13, 2026
8 checks passed
@lroolle
lroolle deleted the feat/pricing-page branch August 13, 2026 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant