DeepSeek's official docs now publish a Claude Code integration contract with Anthropic routing, Web Search support, and Claude-to-V4 model mapping

Checked on June 23, 2026: DeepSeek's official Claude Code page now documents the Anthropic-compatible environment contract, native Web Search support, and an explicit mapping where Claude-style model names route to DeepSeek V4 Pro or Flash.

Accepted official-source monitoring note

Today's accepted item stays DeepSeek-first and uses a current official DeepSeek documentation page because the official @deepseek_ai X timeline still was not safely readable in this run. DeepSeek's English homepage continues to anchor the official X surface, but the direct timeline did not expose a reliably crawlable current post here, so the publish-safe choice is a first-party docs-backed developer update.

What we verified on June 23, 2026

DeepSeek now has an official Claude Code integration page inside the agent-integrations section of the API docs.
The official environment contract is concrete: DeepSeek publishes ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic, uses deepseek-v4-pro[1m] for the main Claude route, keeps deepseek-v4-flash on the lighter lane, and exposes CLAUDE_CODE_EFFORT_LEVEL=max.
DeepSeek explicitly says Web Search is natively supported in Claude Code and that search-triggered summarization creates additional model-token cost.
The same page publishes a model-mapping rule for Claude-style names: claude-opus* maps to DeepSeek V4 Pro, while claude-haiku* and claude-sonnet* map to DeepSeek V4 Flash.
DeepSeek also says this mapping can help with the new Claude Desktop app's developer-mode model-name restrictions, which turns a community workaround pattern into a partially official routing story.

Why this is publishable

This is a current official DeepSeek support page, not a rumor, repost, or inventory change.

It creates a first-party Claude Code setup contract instead of leaving teams on community snippets alone.
It adds operational details developers actually search for: the Anthropic base URL, the Pro-vs-Flash split, Web Search billing behavior, and the Claude-name mapping rule.
It is not a duplicate of the earlier Reasonix, OpenClaw, AstrBot, Langcli, or OpenCode news items already published on the site.

Why this matters for DeepSeek-first SEO pages

Support pages can now target official DeepSeek Claude Code setup rather than screenshot-only walkthroughs.
DeepSeek routing content can explain Anthropic endpoint choice and model mapping without implying that Claude itself is the headline product.
Search-intent pages can separate official facts from analysis around desktop-model restrictions, Web Search cost control, and Pro-versus-Flash routing.

Rejected candidates today

Official X timeline as the primary source: rejected for this run because the homepage anchor remained visible but the direct x.com/deepseek_ai timeline still was not safely readable here.
The official GitHub Copilot page: official and current, but weaker than Claude Code as the single news headline because it centers on a VS Code extension flow already broadly familiar to developers.
The official GitHub Copilot CLI page: official and useful, but better as a support-query guide opportunity than the main news slot because the key insight is a narrow provider-type fix.
The homepage V4 Preview anchor: official, but older and already covered by existing V4 launch and migration pages.
Status-page uptime alone: official, but weaker than a new docs page that changes how developers wire a real DeepSeek-backed coding assistant.

Editorial takeaway

The safest official DeepSeek story today is a Claude Code integration documentation check: DeepSeek's own docs now publish the Anthropic routing contract, native Web Search support, and a documented Claude-name mapping rule that explains how DeepSeek wants this coding workflow to run. That is a stronger current developer signal than recycling an older X anchor we still could not fully verify live.