chore: update deepseek provider docs

[sammaji]

Summary

Updates the DeepSeek provider documentation to reflect that Chat Completions and the Responses API are now routed through DeepSeek's Anthropic-compatible endpoint (/anthropic/v1/messages) rather than the OpenAI-compatible endpoint. Text Completions continue to use the OpenAI-compatible /beta/completions beta endpoint.

Changes

• Updated the overview to describe DeepSeek as a mixed-endpoint provider: Anthropic-compatible for Chat Completions and Responses API, OpenAI-compatible for Text Completions
• Replaced references to OpenAI-compatible chat behavior with Anthropic-compatible equivalents, including authentication (x-api-key instead of Authorization: Bearer), request/response converters, tool calling, and reasoning/thinking parameter mapping
• Removed the documented internal conversion flow where Responses API requests were first converted to Chat Completions — Responses requests are now sent natively to /anthropic/v1/messages
• Removed the filtered parameters section (previously OpenAI-specific exclusions) and the stripReasoningDetails behavior note, as these no longer apply to the Anthropic-compatible path
• Updated the "Known Limitations" accordions to clarify that the user field size limit applies only to Text Completions, and replaced the "Reasoning Details in Assistant Messages" limitation with a "Mixed Endpoint Compatibility" note explaining the two-endpoint architecture and its implications for which provider docs apply

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Review the updated docs/providers/supported-providers/deepseek.mdx to confirm:

• The overview accurately describes the Anthropic-compatible endpoint for Chat Completions and Responses API
• Cross-references point to the Anthropic provider docs instead of OpenAI for chat and responses behavior
• The Text Completions section still correctly references the OpenAI-compatible /beta/completions endpoint
• The known limitations section reflects the current mixed-endpoint architecture

Breaking changes

• Yes
• No

Security considerations

The documentation now explicitly calls out that the Anthropic-compatible endpoint uses x-api-key header authentication rather than a bearer token, which is relevant for operators reviewing how provider credentials are transmitted.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

📝 Walkthrough

Walkthrough

DeepSeek provider documentation distinguishes Anthropic-compatible Chat Completions and Responses endpoints from the OpenAI-compatible Text Completions endpoint, updating routing, authentication, parameter mapping, request handling, and compatibility caveats.

Changes

DeepSeek compatibility documentation

Layer / File(s)	Summary
Endpoint routing and operation compatibility docs/providers/supported-providers/deepseek.mdx	Documents Anthropic-compatible routing for Chat Completions and Responses, OpenAI-compatible routing for Text Completions, and the corresponding configuration options.
Request behavior and compatibility caveats docs/providers/supported-providers/deepseek.mdx	Documents Anthropic authentication, reasoning-to-thinking mappings, native Responses handling, forced tool-choice behavior, extra-parameter handling, and mixed endpoint caveats.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• maximhq/bifrost#5176: Covers the Anthropic-mode routing and endpoint-specific parameter behavior described by this documentation.
• maximhq/bifrost#5208: Adds DeepSeek E2E coverage for the Anthropic and Responses routing behaviors documented here.

Suggested reviewers: akshaydeo, danpiths, roroghost17

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title is concise and accurately summarizes the main change: updating DeepSeek provider docs.
Description check	✅ Passed	The description follows the template well and includes the required summary, changes, type, affected areas, testing, breaking changes, security, and checklist sections.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-14-chore_update_deepseek_provider_docs

---

_{Comment @coderabbitai help to get the list of available commands.}

[sammaji]

• chore: update deepseek provider docs #5177 : 2 dependent PRs (#5187 , #5208 ) 👈 (View in Graphite)
• fix: uses anthropic endpoints in chat completion and responses in deepseek #5176
• fix: adds sgl anthropic compatible apis via key level setting #5305
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[greptile-apps]

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
docs/providers/supported-providers/deepseek.mdx	Updates the DeepSeek provider page to document default OpenAI-compatible routing, optional Anthropic-compatible routing, and endpoint-specific behavior.

_{Reviews (14): Last reviewed commit: "chore: update deepseek provider docs" | Re-trigger Greptile}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/providers/supported-providers/deepseek.mdx`:
- Around line 195-199: Update the “Impact” statement in the “Mixed Endpoint
Compatibility” accordion to limit the OpenAI caveat to endpoint, authentication,
and request/response conversion details. Preserve that shared capabilities such
as reasoning, tools, streaming, and extra_params remain applicable, and retain
the Anthropic documentation cross-reference for Chat Completions and Responses.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: caad0b40-cc4c-4a53-b1a2-cbec9d1a6f13

📥 Commits

Reviewing files that changed from the base of the PR and between 46eed16 and c0d7ee2.

📒 Files selected for processing (1)

• docs/providers/supported-providers/deepseek.mdx

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/providers/supported-providers/deepseek.mdx`:
- Around line 114-116: Remove or relocate the “Extra Parameters” subsection from
the Chat Completions documentation so it is not attributed to that endpoint. If
retained, place it under the provider’s Text Completions operation, preserving
the documented passthrough behavior and endpoint-specific alignment.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 833fe6a6-3d1d-4302-ae0b-c64322c8a56f

📥 Commits

Reviewing files that changed from the base of the PR and between 7455a0a and 2eac7a9.

📒 Files selected for processing (1)

• docs/providers/supported-providers/deepseek.mdx

[akshaydeo]

Merge activity

• Jul 18, 4:02 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 18, 4:04 PM UTC: @akshaydeo merged this pull request with Graphite.

The base branch was changed.