Official2026-06-09

DeepSeek 官网英文首页仍把 @deepseek_ai 的 4 月 24 日 V4 Preview 帖子作为公开 X 入口

截至 2026 年 6 月 9 日，DeepSeek 英文首页仍直接链接到 @deepseek_ai 的 V4 Preview 帖子；与此同时，官方 API 文档继续把 V4 Pro / V4 Flash 作为当前模型名，并保留 7 月 24 日旧别名退役提醒。

中文摘要

截至 2026 年 6 月 9 日，DeepSeek 英文首页仍直接链接到 @deepseek_ai 的 V4 Preview 帖子；与此同时，官方 API 文档继续把 V4 Pro / V4 Flash 作为当前模型名，并保留 7 月 24 日旧别名退役提醒。

阅读提示

这篇中文稿保留原始来源链接，并把 DeepSeek 官方发布、报道和市场传闻分开标注。购买相关判断仍以 /zh/pricing 的真实库存卡片为准；出现在新闻或基准中的模型不代表可购买。

英文原文

Accepted official-source monitoring note

Today's accepted item stays DeepSeek-first and uses the safest public evidence chain available without a logged-in X session: DeepSeek's own English homepage plus DeepSeek's official API documentation.

What we verified on June 9, 2026

  • DeepSeek's English homepage still links directly to an X post from @deepseek_ai as its public social anchor.
  • That linked post is the April 24, 2026 DeepSeek-V4 Preview announcement, which states that V4 Preview is live and open-sourced, names DeepSeek-V4-Pro and DeepSeek-V4-Flash, and says the API was updated that day.
  • DeepSeek's current official API docs still present V4 Pro and V4 Flash as the active public model names, with OpenAI-format and Anthropic-format base URLs unchanged.
  • The same official docs still mark deepseek-chat and deepseek-reasoner for deprecation on July 24, 2026 at 15:59 UTC, which matters for older snippets that still use those aliases.

Why this is publishable even though the linked X post is older

There was no newer official @deepseek_ai post that I could verify safely without login friction or impersonator risk. The stronger present-tense fact is therefore not "DeepSeek posted something new today." It is: DeepSeek itself still chooses that V4 Preview post as the official public X anchor on June 9, 2026.

That is useful for a DeepSeek news index because it:

  1. Confirms @deepseek_ai as the official X account through an official DeepSeek-owned page.
  2. Keeps the site's official-news framing honest about what is directly verified today versus what is only inferred from older launch coverage.
  3. Reinforces that the site's developer pages should still lead with V4 Pro / V4 Flash naming, not legacy aliases.

What this means for DeepSeek-first SEO pages

  • The news index can explicitly describe itself as tracking official DeepSeek X and docs in addition to the three standing developer surfaces.
  • Claude Code, API migration, and agent-integration content should keep the exact V4 model strings visible.
  • Older alias-based examples should be treated as compatibility-only because the official docs now attach a real retirement date to those names.

Rejected candidates today

  • CodeWhale / DeepSeek TUI release chatter: useful for the TUI track, but not official DeepSeek X content.
  • Community summaries of the same V4 launch post: helpful for discovery, but weaker than DeepSeek's own homepage anchor plus official docs.
  • Service status and pricing pages alone: official, but neither provided a stronger X-linked public update than the homepage anchor.

Editorial takeaway

The safest current official-X story is not a fresh product launch. It is a verification update: DeepSeek's own homepage still points the public to the April 24 V4 Preview post from @deepseek_ai, while the official docs keep V4 Pro and V4 Flash as the current developer-facing baseline and keep the July 24 alias retirement visible.

Sources checked

查看原始来源