New DeepSeek Pricing Published (Peak and Off-Peak)

mmittermayr about 4 hours ago 5 comments

ZH version is available. Content is displayed in original English for accuracy.

See here: https://api-docs.deepseek.com/quick_start/pricing/

Peak pricing is twice the price, or, off-peak is half the price.

Peak hours are 01:00 - 04:00 and 06:00 - 10:00 UTC (all other hours are off-peak)

-- V4 FLASH NOW -----------------

Off-peak: $0.007 (cache hit), $0.22 (miss), $0.66 (out)

Peak: $0.014 (cache hit), $0.44 (miss), $1.32 (out)

-- V4 FLASH OLD vs NEW (OFF-PEAK) -----------------

Cache hit: $0.0028 vs $0.007 (+250%)

Cache miss: $0.14 vs $0.22 (+157%)

Output: $0.28 vs $0.66 (+235%)

-- V4 PRO -----------------

Off-peak: $0.022 (cache hit), $0.66 (miss), $1.98 (out)

Peak: $0.044 (cache hit), $1.32 (miss), $3.96 (out)

-----------------

Once the page gets updated and lost in time, to compare, the same page from August 1, 2026: https://web.archive.org/web/20260801170952/https://api-docs.deepseek.com/quick_start/pricing/

⚡ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 186 words in the discussion.

Discussion (5 Comments)Read Original on HackerNews

cheesecakegood•about 3 hours ago

I guess it’s not unexpected per se, but the peak hours are solidly Chinese daytime work hours with an extended lunch break, and hitting a bit of Europe’s morning. But no American peak hours, unless you count after-work hobby coding (6-9 pm Pacific?) which tells you indirectly a bit that American adoption is not a major driver of revenue for them. Or that the after-work ‘hobbyist’ is the main audience, which is also plausible.

sixtyj•about 4 hours ago

DeekSeek did a strategic b2c mistake. It is always easier to start with higher prices and give discounts than go opposite way (=raise).

But people get used to higher prices. Or they churn out.

For hobby projects there can be local or free models. There are also some caching techniques.

mittermayr•about 4 hours ago

Yeah, they onboarded A LOT of folks with that original pricing and quality. It was "good enough" for most use-cases, like many, I work in existing code-bases and do a lot of "multi-file" edits, that aren't hard to do technically, just take a lot of time and must be done precisely enough. For that, it was perfect.

I wonder how many people will stay, there's still a huge void in alternatives on that original pricing.

alxcls•about 3 hours ago

Well I could have done without the improvement if it meant keeping the prices low, might have to find a better model for cheap inference

NullifyNAN•about 3 hours ago

Thank you for old vs new comparison