API Change Watch
EN中文
Menu
Get alerts
Primary official sources. Traceable record by record.Provider docs, changelogs and official announcements only
12primary source pages30verified eventsSep 1, 2026 – Sep 10, 2026 (UTC)
Inspect source registry
Public preview · automatic monitoring and email alerts are not enabled

UTC 2026-09-10 build snapshot, not live metrics. Date states can update; source verification timestamps do not.

Home/Events/DeepSeek
DeepSeek

deepseek-v4-pro routed to V4.1 Flash after Sep 14, 2026

After 12:00 Beijing Time on Sep 14, 2026, all requests to deepseek-v4-pro will be routed to V4.1 Flash and billed at the V4.1 Flash price, pending the release of V4.1 Pro.

HighApi ShutdownVerifiedOfficial Announcement
4d leftSep 14, 2026

Verification is under 30 days old, not a live check; date passage does not confirm shutdown.

What changed

Impact summary

After 12:00 Beijing Time on Sep 14, 2026, all requests to deepseek-v4-pro will be routed to V4.1 Flash and billed at the V4.1 Flash price, pending the release of V4.1 Pro.

BeforeDeepSeek V4 Pro
After / replacementdeepseek-flash (V4.1 Flash) at V4.1 Flash pricing

Affected models and systems

deepseek-v4-pro

Migration action

Recommended next step: After 12:00 Beijing Time on 2026-09-14, migrate deepseek-v4-pro traffic to deepseek-flash before the routing switch; test and verify billing at V4.1 Flash rates.

Source and interpretation

API platform & regional scope

DeepSeek direct API · Direct API; country eligibility not established by the reviewed log.

Not third-party hosting.

Bounded manual review of the registered official sources; not a complete archive.

Unconfirmed regions are not assumed to be global. Automatic monitoring is OFF. Source checks

Official evidence locators

Deadline 12:00 Beijing Time (UTC+8) on 2026-09-14; effectiveAt is the calendar date used by the catalog.

Affected endpoints: Not separately specified; check model / capability scope

Action / deadline: Review required · Stated deadline

This record is classified as official announcement. The facts above were normalized from the provider's public developer documentation. API Change Watch does not treat an unreviewed page diff as a verified announcement.

Record revision history

  • · addition · 3ca1e43b2d6b

Full before/after values are retained in the JSON export. Recording time is not announcement or verification time.

Read the official source ↗