DeepSeek's web search: plan for the cost of a useful answer
DeepSeek’s announced billing date for web lookups in certain coding tools has passed. Check your account and measure the cost of one finished task.
Photo unavailableIf your tool uses DeepSeek for web research, check its current charges and count the lookups behind one useful result before setting a budget.
Check which service your tool uses
If you use DeepSeek to help an app find current information, ask the person managing it to check the account’s latest usage and pricing. Try one ordinary task, then look at the web lookups behind the result.
DeepSeek’s published pricing sets November 1 at midnight in Beijing as the start of per-request billing for certain previously free web tools. That was October 31 at 16:00 UTC. The announced date has now passed.
The notice concerns web searches and page retrieval carried out by DeepSeek when you use its developer service through DeepSeek Harness, Claude Code or Codex. Those tools can connect to different AI providers, so first confirm whether your setup actually uses DeepSeek.
Read the announcement: DeepSeek: Search and Fetch guide, billing rules and announced start date.
Two useful steps have separate prices
Search finds web pages matching a question. Fetch retrieves the content of one page so a tool can read it. A single research task can involve both, sometimes more than once.
DeepSeek currently lists Search at $0.75 per 1,000 successful requests and Fetch at the same rate. They are counted separately. The AI model’s own usage charges are additional.
The guide says a lookup is chargeable only when it succeeds and returns search results or page content. Failed requests, empty search results and timeouts are not billed. Asking for more results within one search does not change that request’s price.
Use the notice to check your own setup
The pricing page still includes the words “currently free” alongside the November 1 start date. We have not inspected individual accounts or verified a charge on your setup. Check the current terms and actual account activity before deciding what the change costs you.
The search tools first became available in October. This is the arrival of an announced billing milestone, rather than a new model launch. It is useful to revisit any practice session or app budget that assumed those web lookups would stay free.
Measure one finished job
For a learning exercise, choose a public-information task whose answer you can verify. Keep private business information out of the first test.
- Confirm the tool is connected to DeepSeek and who manages its balance.
- Choose one question that needs current web information.
- After the task finishes, review successful Search and Fetch requests alongside the model’s usage.
- Check the answer and sources, then agree a sensible budget and who reviews spending.
Make running costs part of learning
Our perspective is that understanding the cost of a completed job is a useful building skill. A clear answer, checked sources and a manageable running cost belong in the same review. Bring that example to training or a build discussion so you can ask specific questions about keeping the tool useful.
Read the original reporting.
Our perspective is based on these sources. Product details and availability can change after publication.
- DeepSeek: Search and Fetch guide, billing rules and announced start dateChecked 2 November 2026
- DeepSeek: Model pricing and Search and Fetch chargesChecked 2 November 2026
- Apidog: DeepSeek Search and Fetch pricing and the October 31 cutoffPublished 28 October 2026
Last updated .
