dsh-web-search-litellm

何时使用 / When to use

Pick this provider when any of these is your situation:

• web_search fails with Authentication Fails, Your api key: ****XXXX is invalid — usually because DEEPSEEK_API_KEY holds a LiteLLM proxy key, not a DeepSeek platform key.
• All company traffic must go through LiteLLM (direct api.deepseek.com is blocked or forbidden).
• You prefer the OpenAI Responses protocol over the Anthropic /messages format.
• You want no free-tier / third-party search service (Tavily, Brave, Exa, …) — search stays on DeepSeek's official server side.
• You use openai/deepseek-v4-flash or openai/deepseek-v4-pro through a LiteLLM proxy as your main model.

Configuration

Settings section web-search-litellm (harness Settings UI) or the bundle patch config:

key	default	meaning
baseURL	$LITELLM_SEARCH_BASE_URL → http://127.0.0.1:4000/v1	LiteLLM proxy root; /responses is appended
model	openai/deepseek-v4-flash	model id routed through the proxy (must support server-side web_search)
apiKeyEnv	LITELLM_API_KEY	credential reference resolved at each search
apiKey	—	optional literal key (secret role)
maxTokens	4096	max_output_tokens for one search request
timeoutMs	60000	per-request timeout; times out as a structured WEB_TIMEOUT error

Known upstream limits (not configuration issues)

• DeepSeek's Responses API documents include as not supported, so structured result items are consumed server-side; sources therefore carry url only (no title/snippet).
• Each search costs one DeepSeek model turn (official mechanism).