跪拜 Guibai
← All articles
Frontend · Backend

DeepSeek Flash 1017 Ships Search and Fetch APIs, Dropping the Barrier to Agent Web Search

By Moment ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Agent developers who want models to search and read the live web get a hosted Search and Fetch API at 5 yuan per 1000 successful requests, replacing hand-built scrapers and result processors. At that price, checking several sources per answer stops being a cost concern.

Summary

DeepSeek Flash 1017 opens two APIs that give agent developers live web grounding. Search finds relevant material and Fetch pulls the page body text, so an agent can locate content, read the full context, then compose an answer. A developer who previously ran their own search tooling reports the switch removed a chunk of tedious work: search result processing and page extraction no longer need maintenance.

Pricing sits at 5 yuan per 1000 successful requests per API. One search plus three page reads runs about two cents, before model invocation fees. At that rate, repeated search rounds and cross-checking sources become affordable inside agent loops.

The same developer flags a rumor making the rounds: the search layer is not Baidu-backed. DeepSeek's official announcement says the search engine is self-developed and has been used long-term, so the quality gains should not be credited to a Baidu partnership.

Takeaways
— Search locates relevant material; Fetch pulls the full web page text, letting an agent read context before answering.
— DeepSeek Flash 1017 exposes both APIs at 5 yuan per 1000 successful requests each.
— One search plus three page reads costs about two cents, excluding model invocation fees.
— Search result processing and page extraction were the burdensome parts the developer had been maintaining by hand.
— DeepSeek officially states it uses its own self-developed search engine long-term, not a Baidu integration.
Conclusions

Search quality is the hard part of web grounding, not just the plumbing: the developer's own implementation worked but underperformed, while the official APIs produced noticeably better results without extra tuning.

The pricing math means agent loops can afford many searches and fetches per task, which changes how aggressively a developer can verify sources before answering.

The need to publicly correct the Baidu rumor shows how quickly assumptions about search backends spread, and official statements are the only reliable source.

Concepts & terms
Search API
An interface that takes a query and returns relevant web content, giving an agent a way to locate material before it reads anything.
Fetch API
An interface that retrieves and extracts the body text of a specific web page, so an agent can read the actual content behind a search result.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗