English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

DeepSeek V4 Peak-Off-Peak API Pricing Takes Effect Today: The 1100% Cache-Hit Hike Explained

Forum topic · 小凯 · 2026-08-17

Summary

DeepSeek has become the first Chinese LLM provider to introduce time-of-use (peak/off-peak) pricing for its V4 API, effective August 17 at midnight Beijing time. During peak hours (9:00-12:00, 14:00-18:00 Beijing time), prices double versus off-peak rates. The steepest increase hits cached input: V4 Pro peak cached-input pricing rises 1100% to 0.3 yuan per million tokens (from 0.025 yuan), with cache-miss input up 200% to 9 yuan and output up 350% to 27 yuan. V4 Flash sees milder hikes (cached input +400%). The move follows massive demand—V4-Flash reportedly processed ~8 trillion tokens on August 1, and the API briefly went down on August 4. The author argues cache-heavy workloads (agents, multi-turn chat, document review, code review) face far larger cost growth than headline percentages, urging developers to re-budget, shift batch tasks to off-peak hours (half price), or switch to alternative models like Qwen or GLM at peak. Strategically, this marks a shift from subsidized customer acquisition to monetizing scale, and could trigger industry-wide adoption of time-based LLM pricing.

DeepSeek has applied the electricity grid's time-of-use pricing concept to large language model APIs.

Starting August 17 at 00:00 Beijing time, the DeepSeek V4 API series officially adopted a rare "peak/off-peak time-of-use pricing" scheme. During peak hours (9:00-12:00 and 14:00-18:00 Beijing time), prices are double the off-peak rates. This is DeepSeek's fourth pricing adjustment announcement since the start of 2026.

The Price Changes

The most striking increase is on cache-hit input. For V4 Pro, peak-hour cached input now costs 0.3 yuan per million tokens, up 1100% from the original 0.025 yuan; cache-miss input is 9 yuan (+200%), output 27 yuan (+350%). Off-peak rates are 4.5 yuan, 13.5 yuan, and 0.15 yuan respectively.

V4 Flash increases are milder: peak cached input 0.1 yuan (+400%), cache-miss input 3 yuan (+200%), output 9 yuan (+350%); off-peak prices are 0.05, 1.5, and 4.5 yuan.

Why DeepSeek Can Do This

DeepSeek's confidence comes from demand pressure. Two dates are frequently cited: on August 1, V4-Flash processed roughly 8 trillion tokens in a single day, and on August 4 the API briefly became unavailable due to traffic overload.

  • Off-peak discount rationale: any developer willing to move tasks to late night/early morning sees bills cut in half.
  • Peak surcharge rationale: compute is scarcest at peak; heavy workloads pay a premium, freeing capacity for low-latency businesses.
  • The Real Impact: Cache-Hit Workloads

    The actual damage sits on the cache-hit line, where the 1100% headline understates the effect. Businesses with high cache-hit ratios see cost growth far exceeding the unit-price increase. Anything relying on large repeated prefixes—agents, multi-turn conversations, document review, code review—will need budgets redone from scratch. DeepSeek is effectively using price signals to redraw the boundary between "cache-heavy" and "generation-heavy" workloads: the former pushed toward off-peak, the latter pushed to pay peak premiums.

    Why This Matters

    This is the first time a Chinese LLM vendor has brought grid-dispatch thinking into LLM API monetization. Before this, the domestic playbook was a three-stage path: undercut to acquire customers (cached input at 1, 0.5, 0.1, then 0.025 yuan) → build scale → raise prices. DeepSeek's execution was notably precise: an August 6 warning in the API docs, a quiet August 12 launch of V4-Pro-0813 raising cached input from 0.025 to 0.1 yuan per million tokens, the formal announcement the evening of August 13, and enforcement at midnight August 17.

    By contrast, Anthropic, OpenAI, and Google Gemini do not offer time-of-use pricing. They either raise prices directly (e.g., GPT-5.6 cached input at $0.05 per million tokens, about 1.25x DeepSeek's post-hike $0.04) or differentiate via subscription tiers (e.g., Claude Max at $200/$400). DeepSeek's peak/off-peak mechanism borrows from spot-instance models of Alibaba Cloud and Tencent Cloud—but this is the first application at the token level.

    What Developers Should Do

  • Cache-heavy workloads: cost growth far exceeds headline increases—re-budget now, and move offline batch processing off real-time peak calls where possible
  • Off-peak scheduling: push night jobs, batch tasks, and deferrable work into off-peak windows for instantly halved unit prices
  • Multi-model strategy: consider falling back to domestic alternatives like Qwen3.8-27B or Zhipu GLM-5.3 during peak hours
  • What It Means for the Industry

  • The "subsidize for scale" phase is over; DeepSeek V4 enters a "scale for profit" phase, where revenue elasticity rises steeply as daily volume climbs past 8 trillion tokens.
  • Chinese LLMs shift from "competing on price" to "competing on pricing mechanisms"—time-of-use, tiered, subscription, token packs, and enterprise contracts will run in parallel.

What to Watch

Over the next 12 months: DeepSeek's actual peak-hour margins, whether off-peak retains developer goodwill, and whether other Chinese vendors (Qwen, Zhipu, Kimi, ByteDance Doubao) follow with time-of-use schemes. If more than two competitors follow within 3 months, the Chinese LLM API market enters a "grid pricing" era.

Tags

#deepseek#api-pricing#time-of-use-pricing#llm-cost#cache-hit#peak-off-peak#china-ai#v4

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178633580