dsh-9router-web-search
由 9router 支持的 DeepSeek Harness 网页搜索和抓取提供程序（ctx.web）。将原生 web_search/web_fetch 工具连接到 9router 的 /v1/search 和 /v1/web/fetch 端点。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:lordraiden/dsh-9router-web-search#58897536f0b8f4039423d40e83f8bef8908a1cc09router Web Search 以 dsh-9router-web-search 发布，当前版本为 0.2.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Web search & fetch for DeepSeek Harness, powered by 9router. Wires the native
web_searchandweb_fetchtools into 9router's/v1/searchand/v1/web/fetchendpoints — no server-side search tool required.
🇺🇸 English · 🇨🇳 简体中文
web_search through 9router's /v1/search, returning deduplicated WebSource results (title, snippet, published date).web_fetch through 9router's /v1/web/fetch, returning clean text/markdown bodies.9router; no manual provider configuration.NINE_ROUTER_API_KEY) or a literal config value; keyless local 9router instances work out of the box; never committed to the repo.DSH's default web_search uses the web-search-deepseek provider, which requires the upstream service to implement Anthropic's web_search_20250305 server-side search tool and return web_search_tool_result blocks.
9router is an OpenAI-compatible gateway: it passes that tool definition to the model as a regular function instead of executing searches server-side — so it cannot provide native search by itself.
web-search-deepseek (default) | 9router (this plugin) | |
|---|---|---|
| Requires | Anthropic web_search_20250305 server-side tool | Any 9router-compatible gateway |
| Works with 9router | ❌ | ✅ |
| Search endpoint | model-provided | POST /v1/search |
| Fetch endpoint | model-provided | POST /v1/web/fetch |
This plugin calls 9router's own endpoints directly and maps their responses to the WebSource and WebFetchBody types expected by the DSH web seam.
web_search / web_fetch (native DSH tools)
│
▼
ctx.web seam
│ provider = "9router"
▼
dsh-9router-web-search
├── search → POST {baseURL}/search → WebSource[]
└── fetch → POST {baseURL}/web/fetch → WebFetchBody
│
▼
9router gateway
│
▼
9router providers / model combos
Errors surface as machine-routable WebError codes (WEB_PROVIDER_ERROR, WEB_TIMEOUT, WEB_ABORTED, WEB_PROVIDER_CREDENTIAL_MISSING); transient network and 5xx failures are retried with backoff; non-2xx fetch responses come back as results — never silent throws.
1. Install the plugin
npx @deepseek-ai/dsh plugin --profile web add github:lordraiden/dsh-9router-web-search
2. Wire it up
web.searchProvider and web.fetchProvider to 9router — no manual wiring needed (a profile's own cordis.patch.yml can override the row).baseURL in the settings card (or a NINE_ROUTER_BASE_URL environment value) pointing at your 9router gateway — there is no implicit fallback endpoint; without a configured endpoint the provider reports itself unavailable.NINE_ROUTER_API_KEY in DSH's credentials — the settings card's API key field writes it there — or set a literal apiKey in the plugin settings. The secret is write-only in the UI and is never stored in this repo. Keyless instances work without any credential.3. Restart & refresh
Restart Harness, then hard-refresh the browser. The 9router options appear in the web settings card.
🔒 Reproducible installs — append a commit SHA to pin an exact version:
npx @deepseek-ai/dsh plugin --profile web add github:lordraiden/dsh-9router-web-search#44d1936
| Key | Type | Default | Description |
|---|---|---|---|
baseURL | string | — | Base URL of your 9router-compatible API (http/https only); resolved as explicit setting → NINE_ROUTER_BASE_URL env → absent (provider unavailable) |
searchModel | string | search-combo | Model name for the search endpoint |
fetchModel | string | fetch-combo | Model name for the fetch endpoint |
searchType | string | web | search_type sent to the search endpoint |
defaultMaxResults | number | 8 | Source cap used only when a search request does not specify maxResults (the DSH seam enforces the per-operation limit) |
timeoutMs | number | 30000 | Shared per-request timeout (per-capability defaults) |
searchTimeoutMs | number | 30000 | Search-only timeout; blank follows timeoutMs |
fetchTimeoutMs | number | 30000 | Fetch-only timeout; blank follows timeoutMs |
fetchFormat | string | markdown | Body format requested from the fetch endpoint (markdown, text, html) |
maxCharacters | number | 50000 | Character cap for fetched bodies; sent to the gateway and enforced locally |
apiKey | secret | — | Literal API key (optional; no key = no Authorization header) |
apiKeyEnv | credential-ref | NINE_ROUTER_API_KEY | Credentials-service key name |
Self-hosted 9router picks its search and fetch backends from its own provider configuration and ignores searchModel/fetchModel; keep those fields set for cloud gateways that route by model.
Endpoint precedence — an explicit baseURL setting wins over the NINE_ROUTER_BASE_URL environment value; with neither set, no endpoint exists and the providers report themselves unavailable. There is no silent fallback to a repository-chosen remote. The schema rejects non-http(s) URLs, empty model/format strings, and non-positive numeric limits before any request is made.
Credentials — NINE_ROUTER_API_KEY is resolved through DSH's credentials service; a literal apiKey is optional and wins when set. apiKeyEnv is a reference name in the credentials service, not a key. The secret is write-only in the settings UI, is never stored in git, and never appears in logs, diagnostics, or error messages.
| Version | |
|---|---|
| Minimum supported | 0.1.7-rc.1 (peer range >=0.1.7-rc.1 <1.0.0) |
| Latest tested | the newest published 0.2.x — CI installs it (currently 0.2.0-rc.2) and runs the full suite against it |
CI runs the contract suite twice: once against the committed peer ranges, and once against the latest 0.2.x. Versions outside the declared range — including future 1.x releases — are not claimed compatible until they are exercised the same way.
The web_fetch capability delegates URL extraction and SSRF protection to the 9router server: the plugin sends the target URL to POST /v1/web/fetch and trusts the gateway's fetch boundary. It implements no local SSRF policy of its own.
Run a patched, current 9router release — the fetch endpoint has a published security advisory:
pnpm install # install dependencies
pnpm test # run the test suite (node:test)
node scripts/validate-pack.mjs # validate the packaged artifact
Node >=20 (CI runs Node 22) and pnpm (CI uses pnpm 10).
Repository layout
dsh-9router-web-search/
├── src/ # server-side plugin: index.js + nine-router-client.js
├── client.js # settings card
├── cordis.patch.yml # bundle patch registering the plugin
├── test/ # node --test contract suite
├── scripts/ # validate-pack.mjs, sync-storefront.mjs
├── .github/workflows/ # CI (tests + packaging, DSH 0.2.x compat) and release
└── package.json # ESM plugin manifest
Releases — stable versions ship as v<version> GitHub Releases matching package.json; the release workflow re-runs the full suite and packaging validation against the tag before publishing.
Storefront sync — node scripts/sync-storefront.mjs syncs the plugin entry into the storefront repo (manual; requires push access to the configured storefront fork).
v<version> GitHub Releases.This project began as a fork of rebron1900/dsh-web-search-9router — thank you for the original 9router-backed web search and fetch provider for DeepSeek Harness.