DeepSeek Keeps V4 Pro API Service After September 14
Current API documentation reverses the planned Pro-to-Flash routing change while legacy Flash aliases still serve V4.1-Flash.
Edited by Tyronne Panaino
DeepSeek's current API documentation says it will continue providing V4 Pro service after September 14, 2026, with its billing method unchanged. That supersedes the V4.1-Flash launch announcement's plan to route Pro requests to Flash from that date. Developers evaluating the transition should use the current service statement when deciding whether a Pro workload needs to move.
The distinction matters because the same documentation still confirms a change for the older Flash models. DeepSeek's September 10 announcement introduced V4.1-Flash with native visual understanding, and the current API table maps the canonical `deepseek-flash` name to that version. Continuing Pro service does not undo the Flash transition.
Pro service continues; legacy Flash aliases change
The current model table maps `deepseek-v4-pro` to DeepSeek-V4-Pro-0813. Its accompanying footnote says the decision to keep Pro service follows user demand and promises further notice if the situation changes. The page does not date that reversal, so this report cannot establish precisely when the revised policy first appeared.
The legacy names `deepseek-v4-flash` and `deepseek-v4-flash-vision-exp` remain accepted, but their original models are retired. The provider says those requests are served by V4.1-Flash and billed at the Flash price. A familiar request identifier therefore does not establish that the older Flash implementation remains in service.
Check the model boundary before changing a workload
For a migration review, record the exact identifier the application sends and the provider's current version mapping. Separate a decision to adopt V4.1-Flash from a decision to continue using Pro. Replay representative requests, inspect the outputs against the application's requirements, and retain the result with the configuration used. These are evaluation recommendations, not findings from a test of DeepSeek's production API.
If a change was planned around the original Pro cutoff, revisit that assumption before executing it. The next source checkpoint is any further service notice or a change to the current model table. Account-level response behavior and billing still need direct verification in the intended environment.
Status
Confirmed provider-policy documentation; medium internal confidence. Both sources are DeepSeek records. They establish the stated service policy and its difference from the original plan, without independently proving routing, billing or comparative model quality.
Sources
Update note: Last reviewed September 15, 2026. The current API service statement supersedes the original Pro routing plan.
Sources
- DeepSeek — V4.1-Flash launch announcement — official
- DeepSeek — current API models and pricing — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.