--- title: "Why Did DeepSeek Double Its API Prices in August 2026? The Take Inside China" date: 2026-08-26 originalDate: 2026-08-14 originalTitle: "DeepSeek涨价背后，一个时代结束了" issue: "Issue 1" description: "DeepSeek's Aug 17 peak/off-peak repricing, read inside China: why developers called it the end of an era when the price-war leader charges real money." tags: - "DeepSeek" - "API pricing" - "V4" - "China AI" sources: - label: "DeepSeek official pricing page (canonical)" url: "https://api-docs.deepseek.com/quick_start/pricing/" - label: "Reuters: DeepSeek raises API pricing for its V4 models (2026-08-13)" url: "https://www.reuters.com/world/china/deepseek-raises-api-pricing-its-v4-models-2026-08-13/" - label: "Quartz: DeepSeek raising API prices by up to 1,100% (2026-08-13)" url: "https://qz.com/deepseek-api-price-increase-v4-peak-off-peak-081326" - label: "r/DeepSeek community reaction" url: "https://www.reddit.com/r/DeepSeek/comments/1vn81do/deepseek_just_massively_increased_their_api/" faq: - q: "Did DeepSeek raise its API prices in 2026?" a: "Yes. Announced the evening of 2026-08-13, effective 2026-08-17 00:00 Beijing time: weekday peak hours (9–12, 14–18) cost roughly double, off-peak is half of peak, and cached-input prices rose sharply — Chinese coverage said up to 12×, Western coverage up to 1,114%; the official pricing page is canonical. The consumer app and web versions remain free." - q: "Why did DeepSeek raise API prices?" a: "The read inside China: the subsidy-era price war is over. After a year of selling at 20–25% of list prices, peak-hour compute was queuing and rate-limiting paying customers. DeepSeek launched V4-Pro the same day (1M-token context) and moved to grid-style time-of-use pricing — a bet that customers now stay for capability, not discounts." - q: "Is the DeepSeek app still free after the August 2026 price change?" a: "Yes. The 2026-08-13 announcement raised API prices only; the consumer app and web versions remain free, per the announcement as translated here and confirmed by the official pricing docs." --- On the evening of August 13, 2026, DeepSeek announced an API pricing change taking effect August 17 at 00:00 Beijing time, roughly doubling peak-hour prices and raising cached-hit input prices by up to 12×. The consumer app and web versions remain free; the change affects API customers. Our original Chinese essay argued this marks the end of China's LLM price-war subsidy era and DeepSeek's shift from "burning money for market share" to commercial sustainability. ## The numbers - Announcement: evening of 2026-08-13; effective 2026-08-17 00:00 Beijing time - 9.11 million views on the trending tech topic inside China [unverified] - Peak-hour prices roughly doubled for some tiers; off-peak is half of peak - Peak hours: weekdays 9:00–12:00 and 14:00–18:00 - V4-Flash peak output: ¥9 per million tokens; off-peak ¥4.5 - V4-Pro peak output: ¥27; off-peak ¥13.5 - V4-Pro launched the same day, with a 1M-token context window - Over the prior year, DeepSeek repeatedly cut prices to 20–25% of original levels - **Figure arbitration:** our Chinese source says cached-hit input rose "up to 12×"; Reuters/Quartz reported up to ~1,114%. Same order of magnitude, different anchor tiers — the [official pricing page](https://api-docs.deepseek.com/quick_start/pricing/) is canonical. ## The take inside China The essay's core argument: stop panicking — this is what a company growing up looks like. DeepSeek borrowed the electric grid's decades-old playbook: time-of-use peak/off-peak pricing. Weekday daytime hours cost more; everything else is half price. Crucially, the consumer app stays free — only API callers pay more. The context is a brutal year-long price war, in which DeepSeek repeatedly sold at 20–25% of list prices, pulling enterprises, agent developers, and AI startups onto its platform. The cost: peak-hour compute crunches — GPU queues and rate-limiting became routine, meaning paying customers got throttled service. Losing money on share while degrading service for payers is not a durable model. The V4-Pro launch matters too: it shipped the same day with a 1M-token context window and agent/coding improvements, benchmarked against top overseas models [unverified]. Off-peak pricing is actually friendlier than before for batch offline inference. The bundle: prime-time compute for those who truly need it; shift to nights at half price. The signal: the subsidy era is officially over; market share bought with losses must eventually be repaid with price increases, and a perpetually bleeding company cannot fund the next breakthrough. DeepSeek raising prices now means it believes customers stay for capability, not discounts. The essay also self-criticizes: peak pricing shifts costs onto callers — small teams and solo developers reliant on daytime peaks are genuinely hurt, and skeptics reasonably ask how much of this is congestion relief versus revenue. ## Why it matters outside If DeepSeek — China's price-war leader — is pivoting to profitability, the era of anomalously cheap Chinese model APIs may be ending, with likely follower moves across the industry. It is also a confidence signal: capability, not discounts, is now expected to retain enterprise customers — a data point for anyone benchmarking Chinese frontier models against Western ones. ## Sources - [DeepSeek official pricing page (canonical)](https://api-docs.deepseek.com/quick_start/pricing/) - [Reuters: DeepSeek raises API pricing for its V4 models](https://www.reuters.com/world/china/deepseek-raises-api-pricing-its-v4-models-2026-08-13/) - [Quartz: DeepSeek raising API prices by up to 1,100%](https://qz.com/deepseek-api-price-increase-v4-peak-off-peak-081326) - [r/DeepSeek community reaction](https://www.reddit.com/r/DeepSeek/comments/1vn81do/deepseek_just_massively_increased_their_api/) > **Provenance & disclosure.** Originally published in Chinese on our WeChat channel on 2026-08-14 ("DeepSeek涨价背后，一个时代结束了"); drafted with AI assistance under human editorial direction. Translated to English on 2026-08-26 (AI-assisted, human-reviewed). Figures are cross-checked against the sources above; claims we could not verify carry [unverified] tags. This is translated commentary — not a SigPulse measurement. Our first-party measurements live in the [dispatches](/posts/) and the [/data/ ledger](/data/).