The Search API and the Fetch API give agents and RAG applications access to live web content: Search API finds web pages for a query and returns structured results. It is powered by DeepSeek's in-house search engine. Fetch API retrieves a single web page and returns its content as Markdown. Both are raw JSON APIs. They use the same bearer authentication as the DeepSeek API. The base URL is https://api.deepseek.com : See the Search API Reference and Fetch API Reference for the complete request and response schemas. Authentication ​ Send your API key and the JSON content type in the request headers: Request fields: Unknown fields in the request body are ignored. Query Operators ​ The query is forwarded with its search syntax intact. The examples below combine operators with a search term; you can combine multiple operators in one query. A successful request returns HTTP 200 with a results array. A normal search with no matches returns an empty array.

Each item in results contains: Request fields: Fetching is subject to the target site's availability and access policies. Errors follow the OpenAI-compatible error format. The param field is always null . Search and Fetch are read-only. For HTTP 408, 429, or 5xx errors, wait and retry. For HTTP 402, top up your account before retrying. Do not retry other 4xx errors without changing the request. Search and Fetch are billed per successful request, not by tokens or by the number of returned results: A request is billable only when it returns HTTP 200 and produces a result (Search must return a non-empty results array, and Fetch must return page content). Failed requests, empty search results, and timeouts are not billed. count only controls how many results are returned and does not affect the per-request price. Note: when you use the DeepSeek API through DeepSeek Harness, Claude Code, or Codex, server-side tool calls already hit the Search and Fetch APIs. These calls are currently free of charge; per-request billing starts at 00:00 Beijing time on November 1, 2026. For each account, Search and Fetch are limited independently, and traffic to one does not consume the other's quota: The QPS (requests per second) limits are calculated at the account level, regardless of which API key is used, and are separate from the model concurrency limits. Requests above the account-level QPS limit receive HTTP 429. In addition to the account-level limit, Fetch is also subject to a per-domain QPS limit, and requests above that limit also receive HTTP 429. Search API Request Query Operators Response Query Operators Fetch API Request Response