DeepSeek API web search: what works and what it ignores

Can the DeepSeek API search the web? Yes, but only through one door. DeepSeek API web search runs when you call the Anthropic-format endpoint, the way Claude Code does. The Responses API ignores the `web_search` tool without an error, and every format ignores `mcp_servers`. So the old answer "DeepSeek cannot search" is wrong, and "just add the tool" is only half right.

DeepSeek V4.1 Flash came out on 2026-09-10, and the top results for this question are still a year old. This page reads DeepSeek's own docs, lists what each API format does with search and MCP fields, and shows how to give a DeepSeek agent the data that native search does not reach: Google results, full pages and company records.

Does the DeepSeek API have web search?

Yes, on the Anthropic-format endpoint, `https://api.deepseek.com/anthropic`. DeepSeek's guide for Claude Code says "The DeepSeek API natively supports the Web Search feature in Claude Code", and that the search runs "through the API provided by DeepSeek" (DeepSeek Claude Code guide, read 2026-10-14). The other formats do not offer it.

Here is what each format says about search and MCP. Sources: the Anthropic API guide and the Responses API guide, both read 2026-10-14.

The Responses guide says unsupported parameters are "silently ignored and do not cause errors". That is the trap. A Responses request with a `web_search` tool returns a normal answer, and the model answers from training data without telling you it never searched.

What does DeepSeek API web search cover, and what does it ignore?

It covers a general web search the model decides to run, with results summarized back into the conversation. DeepSeek warns that this costs extra: the search "generates additional LLM API requests to summarize the retrieved search content". It ignores MCP servers in the request, and the docs say nothing about which search engine answers, domain filters, locations or how many results come back.

So treat it as a quick lookup, not as a data source you can steer. If your agent needs Google's own ranking for a keyword, the text of a specific page, or a company's headcount from its domain, native search will not give you that in a form you can check. Those jobs need tools of their own.

What is DeepSeek V4.1 Flash?

It is the smallest model in DeepSeek's new architecture family, with native visual understanding, released on 2026-09-10 (DeepSeek news, read 2026-10-14). You call it as `deepseek-flash`, and the Anthropic format maps any Claude Sonnet or Haiku model name to it.

Off-peak, `deepseek-flash` costs $0.15 per 1M input tokens on a cache miss and $0.6 per 1M output tokens, and peak hours cost twice that (DeepSeek pricing, read 2026-10-14). The pricing page lists no separate search fee, only the extra tokens. For comparison, Claude's web search tool is $10 per 1,000 searches plus tokens (Anthropic pricing, read 2026-10-14), and OpenAI's is $10 per 1,000 calls plus search content tokens (OpenAI pricing, read 2026-10-14).

How do I add data tools to DeepSeek API web search?

Give the model tools that your side runs. Every DeepSeek format supports function tools: the model asks for a call, your code or client runs it, and the result goes back as a tool result. There are two ways to set that up.

1. MCP in the client. MCP has to live in the client, not in the API request. A client such as Claude Code starts your MCP servers on your machine and offers their tools to the model as ordinary tools. Point Claude Code at DeepSeek as its guide shows, and the MCP servers you added still work, because Claude Code calls them, not DeepSeek. This is the shortest path if you already use an agent harness.

2. A function tool in your code. If you call the API from your own program, define a function with a JSON schema, run it when the model asks, and send the answer back. LLM tool calling with live APIs walks through that loop, and MCP vs API for agents helps you pick between the two.

Either way, the tools behind it can share one looot key instead of a search account, a SERP account and an enrichment account. The table reads today's cheapest price for each job from the live catalog.

The job pages say what each one returns: web search API, Google SERP API, URL to markdown and company enrichment.

What this post does not cover

• We did not send a live DeepSeek request. Everything about DeepSeek here comes from its docs as read on 2026-10-14, and DeepSeek can change them.
• looot does not host DeepSeek models or sell DeepSeek tokens. You keep your own DeepSeek key and bill.
• looot cannot make DeepSeek's API call an MCP server. The MCP connection lives in your client.
• The chat app at chat.deepseek.com is a different product from the API. This post covers the API only.
• A data tool returns what the provider finds. It does not check facts for you, so ask the model to cite each source.

Last checked 2026-10-14 against DeepSeek's docs, the vendor pricing pages linked above and the live catalog.