DeepSeek's official Claude Code guide publicly documents native Web Search and keeps Pro-for-main, Flash-for-subagents routing

Checked on June 10, 2026: DeepSeek's official Claude Code page says the DeepSeek API natively supports Web Search in Claude Code, while the same vendor page still pins the main model to V4 Pro and subagents to V4 Flash.

Accepted official-source monitoring note

Today's accepted item stays DeepSeek-first and uses current official DeepSeek documentation because the public X surface is still login-friction-heavy and did not expose a newer safely verifiable post than the already-published homepage anchor from the prior run.

What we verified on June 10, 2026

DeepSeek's official Claude Code integration page explicitly says the DeepSeek API natively supports the Web Search feature in Claude Code.
That same official page still keeps the main coding route on deepseek-v4-pro[1m] and the subagent route on deepseek-v4-flash.
DeepSeek's API quick-start still lists only V4 Flash and V4 Pro as the primary public model names, while marking deepseek-chat and deepseek-reasoner for deprecation on 2026-07-24 15:59 UTC.
DeepSeek's English homepage still points its public social anchor to @deepseek_ai, which helps confirm the official account even though the X page itself is not safely crawlable here.

Why this is publishable

This is not framed as a brand-new product launch. It is a current official documentation signal that matters for real developer behavior:

It shows DeepSeek is not only documenting endpoint replacement for Claude Code, but also documenting a first-party Web Search path through the same integration surface.
It preserves a clear Pro-versus-Flash routing contract on the same page, which is stronger than community screenshots or reposts.
It gives the news index a fresh official topic that is not a duplicate of the June 9 homepage-X anchor verification.

Why this matters for DeepSeek-first SEO pages

Claude Code guides should treat Web Search support as an official DeepSeek capability, not only a community workaround topic.
API-routing guides should keep Anthropic-format and OpenAI-format endpoints separated clearly, because Claude Code depends on the Anthropic-compatible route.
Migration pages should continue replacing old alias names before the July 24, 2026 cutoff.

Rejected candidates today

The same April 24 homepage X anchor: still official, but already published on June 9 and therefore a duplicate-content risk for today's news slot.
Community X reposts or summaries of Claude Code behavior: weaker than the vendor page that now states Web Search support directly.
Status page and pricing page alone: official, but neither carried a stronger fresh editorial angle than the current Claude Code integration page.

Editorial takeaway

The safest official DeepSeek story today is a Claude Code documentation check: DeepSeek's own guide now publicly spells out Web Search support, while keeping the main-model route on V4 Pro and the subagent lane on V4 Flash. That is a stronger guide-shaping signal than generic market chatter and stronger than repeating yesterday's X-anchor verification.