What changed
The September 10 V4.1 Flash announcement said all deepseek-v4-pro requests would route to Flash at Flash rates starting September 14. DeepSeek's official API Change Log now explicitly says it decided, in response to user demand, to continue V4 Pro API service after September 14 with unchanged billing. The current Models & Pricing page lists deepseek-v4-pro as DeepSeek-V4-Pro-0813, with distinct Pro prices and a 500 concurrency limit. The older product announcement still says the opposite; this is a documented contradiction, not independently verified live routing.
Why it matters
Developers who budgeted Flash rates or migrated away from V4 Pro on the original announcement may be relying on superseded instructions. The current rate card and changelog point to distinct Pro and Flash service and billing. Teams should verify the actual model and charges on their own account, rather than infer routing from the older announcement.
The current changelog contradicts the original transition
The older September 10 product announcement schedules a V4 Pro-to-Flash reroute from September 14. The official API Change Log for the same release says V4 Pro service continues after September 14 with unchanged billing. Neither page explicitly explains the reversal.
The live rate card retains a distinct Pro model and price
The current Models & Pricing page lists deepseek-v4-pro as DeepSeek-V4-Pro-0813. Its peak cache-miss input/output rates are $1.32/$3.96 per million tokens, versus $0.30/$1.20 for Flash. Off-peak rates are half peak. This is published pricing, not a tested invoice.
Flash compatibility aliases are a separate confirmed change
The same current pricing page explicitly says the retired deepseek-v4-flash and deepseek-v4-flash-vision-exp names route to V4.1 Flash. That does not establish the disputed V4 Pro reroute.
Operational checks should separate backend identity and billing
Pin and inspect model metadata where available, compare invoices with the current rate card, and run task-level regression tests. A stable model string does not always imply stable behavior, but a contradictory marketing page does not prove a reroute occurred.