Review found two faults in the endpoint and configuration checks. The providers took the official chat route's endpoint from the first active dsh-llm-deepseek-api-key Loader row, so a composition that isolates several instances answered for an unrelated one: a correct route lost search, or a gateway's key reached DeepSeek. And a key saved on the Web search settings page lands under the default DEEPSEEK_API_KEY reference, so the inference that search had its own configuration never saw it. Both DeepSeek web packages now serve only the deepseek-account and deepseek-official routes, whatever key they are configured with, and no longer compare the chat endpoint with their own. ready() checks the route and then credential presence as before; the API-key resolver repeats the route check and refuses with WEB_PROVIDER_ROUTE_DISABLED. The packages no longer read Loader rows or depend on dsh-llm-deepseek-api-key, so the lockfile, the module graph, and the keyless smoke expectations that the endpoint check had changed return to master's. An upgrade guide covers conversations on other providers' models, which lose DeepSeek web search and, with the Search and Fetch APIs selected, web_fetch.
description, kind
| description | kind |
|---|---|
| Package map for the web access capability family: the search/fetch service, its provider backends, and the model-facing tools that consume them. | package-group |
web/ — web access capability family
English | 中文
Summary
The web/ packages let models search the public web and fetch HTTP(S) pages through the web_search and web_fetch tools. Deployments can choose Exa, Perplexity, or DeepSeek for search and anonymous HTTP(S) or DeepSeek for fetch; availability and resource limits depend on the configured provider. Use this family for search and page retrieval, not interactive browsing, content extraction, or per-URL policy enforcement. Models receive consistent tool behavior, cancellation, and error reporting when providers change.
Table of Contents
Packages
Six packages play the web roles; the subsystem reference owns the exhaustive vocabulary and contracts.
| Package | Role | ctx key |
|---|---|---|
web/ |
Search/fetch service: search and fetch URLs through interchangeable backends, one selection and error policy | ctx.web |
web-search-exa/ |
Searches the web through Exa | registers on ctx.web |
web-search-perplexity/ |
Searches the web through Perplexity | registers on ctx.web |
web-search-deepseek/ |
Searches through DeepSeek Messages | registers on ctx.web |
web-deepseek-api/ |
Searches and fetches pages through the DeepSeek Search and Fetch APIs | registers on ctx.web |
web-fetch-http/ |
Fetches HTTP(S) pages anonymously | registers on ctx.web |
tool-web/ |
Exposes web_search and web_fetch to the model |
registers on ctx.tools |
Related documentation
Start with the subsystem reference for the shared vocabulary, then the design decision behind the single provider-selection service.
- Web subsystem — the search/fetch requests and results, provider availability,
WebError, and the fetch network policy. - Web capability seam decision — why search and fetch share one provider-selection service.
Dev Note
Working context for maintainers — click to expand
None.