Fetch API
A Web standard specification that defines how HTTP network requests and responses are made through the Fetch interface, providing interfaces such as Request, Response, and Headers.
Core Facts
DeepSeek launched a Search and Fetch API, split into two layers of capability: Search retrieval and Fetch web content extraction.
The DeepSeek search and scrape API is billed at $0.75 per 1,000 successful requests, i.e., $0.00075 per successful request, and the count parameter does not affect the price.
DeepSeek released the V4.1-Flash-1017 model on October 17, adding the Search and Fetch APIs.
Timeline (last 90 days)
The Search API limit is 100 QPS per account, and the Fetch API limit is 25 QPS per account.
External search calls should set a timeout to avoid indefinitely hanging the worker process.
One search followed by fetching five pages is six API calls, not one, so cost should be calculated separately by number of calls.
Directly calling the two APIs Search and Fetch does not amount to having a research agent, because decision logic, source review, error recovery, and cost control are still missing.
Research agents and retrieval APIs are two different layers: a retrieval API is only responsible for fetching external information, whereas a research agent is a loop system that plans questions on its own, decides what to search for, which pages to select, and how to integrate the answers.
These two APIs use a billable-on-success model: a Search is billed only when it returns HTTP 200 with non-empty results, and a Fetch is billed only when it returns page content; empty results, failed requests and timeouts are not charged.
Search accepts a required query parameter, an optional result count count between 1 and 50, and a need_content parameter; Fetch accepts a URL and returns a title plus Markdown content.
The Search and Fetch APIs are both priced at USD 0.75 per 1,000 successful requests.
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.
The Fetch API (POST /v1/tools/fetch) accepts a URL and returns the page content in Markdown format, at the same price and rate limit as the Search API.
9 more timeline events
All Facts (19)
DeepSeek launched a Search and Fetch API, split into two layers of capability: Search retrieval and Fetch web content extraction.
70%Partially VerifiedThe DeepSeek search and scrape API is billed at $0.75 per 1,000 successful requests, i.e., $0.00075 per successful request, and the count parameter does not affect the price.
65%UnverifiedThe Search API limit is 100 QPS per account, and the Fetch API limit is 25 QPS per account.
50%UnverifiedDirectly calling the two APIs Search and Fetch does not amount to having a research agent, because decision logic, source review, error recovery, and cost control are still missing.
50%UnverifiedResearch agents and retrieval APIs are two different layers: a retrieval API is only responsible for fetching external information, whereas a research agent is a loop system that plans questions on its own, decides what to search for, which pages to select, and how to integrate the answers.
50%UnverifiedThese two APIs use a billable-on-success model: a Search is billed only when it returns HTTP 200 with non-empty results, and a Fetch is billed only when it returns page content; empty results, failed requests and timeouts are not charged.
50%UnverifiedSearch accepts a required query parameter, an optional result count count between 1 and 50, and a need_content parameter; Fetch accepts a URL and returns a title plus Markdown content.
50%UnverifiedSearch 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.
50%UnverifiedThe Search and Fetch APIs are both priced at USD 0.75 per 1,000 successful requests.
50%UnverifiedExternal search calls should set a timeout to avoid indefinitely hanging the worker process.
50%UnverifiedOne search followed by fetching five pages is six API calls, not one, so cost should be calculated separately by number of calls.
50%UnverifiedThe Fetch API (POST /v1/tools/fetch) accepts a URL and returns the page content in Markdown format, at the same price and rate limit as the Search API.
50%UnverifiedThe key names of the Headers interface are case-insensitive and are normalized on access, and it supports methods such as append, get, and has, and can be passed between Request and Response.
50%UnverifiedThe Fetch API is a new-generation network request interface standardized around 2015 alongside Service Worker, designed based on Promises.
50%UnverifiedReplay XHR cannot correctly reproduce Fetch requests, which is the fundamental reason it was replaced by Resend.
50%UnverifiedHeaders 是 Fetch API 提供的标准接口，用于表示 HTTP 请求/响应头，内部以规范化方式存储键值对（键名统一小写、合并重复项），并通过 get、set、append、has 等方法访问，而非属性读取。
50%UnverifiedJavaScript in the browser cannot create raw TCP/UDP sockets; all network communication must go through high-level APIs such as WebSocket, Fetch, and WebRTC.
50%Partially VerifiedDeepSeek released the V4.1-Flash-1017 model on October 17, adding the Search and Fetch APIs.
65%UnverifiedDeepSeek opened its search API on the morning of October 17, priced at 5 yuan per 1000 calls, free until November 1.
50%