DeepSeek opens search, file and voice tools to developers
DeepSeek’s official API docs now list web search, file input, URL reading, OCR-related tools and voice services for developers.
DeepSeek says developers can now access the same family of application tools behind its consumer-facing service through APIs, with web search, file input, URL reading, model safety, automatic speech recognition and text-to-speech all listed in its official documentation.1
The Search API is exposed through a POST request to `https://api.deepseek.com/v1/tools/search`. Developers send a query and can request between one and 50 results. The documentation says the endpoint returns ranked, structured results with titles, URLs, snippets, summaries and page content when retrieval is enabled.1
DeepSeek also documents operators such as `site:`, `-site:` and quoted phrases. An optional original question can be supplied to improve query understanding, while localisation is available as an additional request field. The page says the API can return page content when `need_content` is set, although the default is false.1
The documentation confirms availability and the shape of the Search API, but it does not provide a full product announcement on the page itself. Pricing, the broader rollout scope and rate limits beyond the published request schema remain unverified here. Developers should therefore treat the documentation as the source of truth for the endpoint, rather than assuming that every application feature has identical access terms.1
Our opinion
Opening application-level search and retrieval tools matters because it gives developers a clearer route to build DeepSeek-powered products without recreating every web-search or document-ingestion layer themselves. The useful part is the structured interface: ranked results, optional content and familiar query operators are easier to plug into an agent or research workflow than a screen-scraped consumer feature. The caveat is equally important. Until DeepSeek publishes pricing, limits and rollout details in one place, this is an API availability story, not proof that the tools are ready for unlimited production use.