Unverified50% confidenceFactExact time
Search and Fetch use the same endpoint prefix; the endpoints given in the official guide are POST https://api.deepseek.com/v1/tools/search and POST https://api.deepseek.com/v1/tools/fetch, both using a Bearer API key and a JSON request body.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedHeaders 是 Fetch API 提供的标准接口，用于表示 HTTP 请求/响应头，内部以规范化方式存储键值对（键名统一小写、合并重复项），并通过 get、set、append、has 等方法访问，而非属性读取。67% similarUnverifiedv1.12.0 adds a url_sources parameter to the web_fetch tool configuration for hosted Agents.63% similarUnverifiedTruthPulse's V1 version had the Agent pass a `url` string to the search tool, but the LLM does not know real URLs, so it fabricated dead links; after V2 changed to passing a `query: string` search keyword, the problem disappeared.62% similarUnverifiedThe web fetch tool built into DeepSeek Harness is a read-only tool that does not carry cookies or credentials and does not render pages like a browser, making it unable to complete operational tasks that require login or clicking.61% similarUnverified静态站点添加搜索功能通常依赖客户端方案，如构建时生成JSON索引文件并在浏览器端使用Lunr.js或Fuse.js进行模糊搜索61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067896API
curl https://kongchang.com/api/v1/knowledge/claims/1067896MCP
get_claim(id=1067896)