DeepSeek has initiated an operational API transition that is more critical for billing and model ID continuity than for launching a new product. Starting at 04:00 UTC on September 14, 2026 (noon Beijing time), every request sent to the deprecated model identifier deepseek-v4-pro will be redirected to DeepSeek-V4.1-Flash and billed according to V4.1-Flash rates.
The company states that this redirection will remain in effect until the release of DeepSeek-V4.1-Pro. Thus, integrations using the Pro tag will continue to function without requiring code changes, although the underlying model and pricing table will change underneath it.
This step differs from the general release of V4.1-Flash, which occurred on September 10. This release introduced the smallest member of the new DeepSeek architectural family—a mixture-of-experts design with 552 billion parameters, actively utilizing about 8 billion parameters at input and 16 billion at output. It also includes native multimodal support and a Causal Encoder–Decoder layout. Official notes also announced the withdrawal of V4-Flash and V4-Flash-Vision-Exp models as standalone products; to ensure compatibility, the identifiers deepseek-v4-flash and deepseek-v4-flash-vision-exp now point to V4.1-Flash. For new integrations, it is recommended to use the deepseek-flash identifier on the unchanged DeepSeek API endpoint.
The second part of the transition concerns pricing. DeepSeek asserts that tests conducted by various parties have shown that V4.1-Flash outperforms V4-Pro in performance, cost, speed, and overall latency, leading the company to gradually phase out V4-Pro as a separately maintained model. After the September 14 switch, traffic with the Pro tag inherits the Flash pricing tables (both peak and off-peak), with off-peak rates remaining half of the peak, instead of the higher Pro schedules that were in place before the redirection. Teams leaving deepseek-v4-pro active automatically adopt the Flash economics but lose the assumption that the Pro identifier still corresponds to previous Pro weights or latency profiles. All cache hit and miss inputs, as well as output tokens, follow the Flash schedule after the routing change.
DeepSeek has not yet published a release date for V4.1-Pro. Until then, the Pro alias serves as a temporary bridge, not a frozen service. Official partners WorkBuddy, including CodeBuddy, and OpenCode already support V4.1-Flash. For operators, the practical checklist is limited: they need to conduct private regression tests against deepseek-flash before or immediately after the UTC switch, update monitoring so that logs and cost dashboards reflect the served model rather than the requested alias, and treat deepseek-v4-pro as a deprecated route until V4.1-Pro arrives. The main focus today is on API infrastructure—who answers the Pro identifier, at what rate, and for how long—rather than the second pass narrative on Flash GA.


