{"slug": "deepseek-opens-its-in-house-search-engine-to-developers", "title": "DeepSeek Opens Its In-House Search Engine To Developers", "summary": "DeepSeek opened its in-house search engine to developers on Oct. 17 through a Search API priced at $0.75 per 1,000 successful requests, with each result carrying an authority tier from 0 to 4 (-1 for unknown) and a rerank score from 0 to 3, where 1.5 or higher is considered high quality. DeepSeek's changelog states the engine indexes hundreds of billions of web pages and handles hundreds of millions of search requests a day, and that it filters SEO spam, \"GEO manipulation,\" and low-quality AI-generated content, though the company has not defined GEO manipulation or described how its detection works. The launch pages do not identify a crawler for the search index or the user agent used by the companion Fetch API, and DeepSeek's privacy policy, last revised Feb. 10, still says the company shares user keywords with third-party search APIs, while Bocha describes itself as DeepSeek's official web search supplier in a GitHub README that DeepSeek does not reference.", "body_md": "DeepSeek opened its in-house search engine to developers on Oct. 17, and the company’s [changelog](https://api-docs.deepseek.com/updates) says the engine filters SEO spam, “GEO manipulation,” and low-quality AI-generated content.\n\nEach result from the new [Search API](https://api-docs.deepseek.com/guides/search/) includes an authority tier for the page and a relevance score, and the API accepts site: queries that limit results to one domain.\n\n## What DeepSeek Says About Its Engine\n\nDeepSeek’s changelog says its in-house engine handles search on its website and in its API, indexes hundreds of billions of web pages, and takes in hundreds of millions of search requests a day from around the world.\n\nGEO (generative engine optimization) is when you shape your content to be cited by AI answer engines. DeepSeek’s changelog states that they credit strict detection as the source of filtering; however, it has not defined what GEO manipulation is or described how their detection process operates. On May 15, Google [said](https://developers.google.com/search/updates#clarifying-that-spam-policies-apply-to-generative-ai-responses-in-google-search) “our spam policies also apply to generative AI responses in Google Search.”\n\nThe [privacy policy](https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html) of DeepSeek was last revised Feb. 10, which states that the company integrates “third-party APIs to provide search services” and shares users’ input keywords with these companies. A Chinese-based search API company called Bocha states they are the official web search supplier of DeepSeek in the customer section of a GitHub [README](https://github.com/bochaai/bocha-search-mcp) for one of their products. DeepSeek does not reference Bocha in their launch pages. The changelog and the privacy policy do not state if any web search queries are still sent to a third party service. Dan Petrovic from DEJAN referenced both the privacy policy and the GitHub README in his [post](https://dejan.ai/blog/deepseek-search-engine/) about the DeepSeek launch.\n\n## What The Search API Returns\n\nEach Search API result contains an authority field; authority fields range from 0 to 4 with -1 being unknown. According to DeepSeek’s [API reference](https://api-docs.deepseek.com/api/search), pages with tiers of 3+ are described as “highly authoritative” sources.\n\nThe rerank score (another field) is a scale of 0-3 and incorporates signals that include relevance, authority and freshness. A rerank score of 1.5+ is considered high quality. The guide and the reference do not explain how a page receives its tier or score.\n\nEach result also comes with a snippet for display, typically 100 to 200 characters, and a summary meant for a model to read, typically 600 to 800 characters. Page content comes back too when a request asks for it and the content is available. Queries can be limited with site: and filtered by language and date published.\n\nSearch and Fetch each cost $0.75 per 1,000 successful requests. Searches that return no results aren’t billed, and requesting 50 results costs the same as requesting just one.\n\n## What DeepSeek’s Pages Say About Crawling\n\nDeepSeek’s Fetch API was released with Search. Fetch provides a single Markdown page and “is subject to the target site’s availability and access policies,” as per the guide.\n\nAccording to the [EU summary](https://cdn.deepseek.com/policies/DeepSeek_Template_for_the_Public_Summary_of_Training_Content_for_GeneralPurpose_AI_model.pdf) of the data used to train DeepSeek-V4, the crawler is “designed to respect robots.txt instructions and other standard web protocols, where applicable.” However, the summary does not identify which crawler this refers to.\n\nAdditionally, none of the launch pages (the guide, API references, changelog and [announcement](https://api-docs.deepseek.com/news/news261017)) provide identification of a crawler for the search index nor do they provide information on what user agent Fetch uses.\n\nIn addition to providing information about several crawlers, the [Known Agents](https://knownagents.com/agents/deepseekbot) bot directory lists a DeepSeekBot user agent and describes it as an AI training data crawler.\n\n## Why This Matters\n\nWith a funded DeepSeek API account, individual site: searches are under $0.01. Each site: search can return up to 50 pages from your website; each page has both an authority tier and a relevance score for that query. If you see a missing result, it could be because the page was either outside the index or caught by filters described in DeepSeek’s changelog, or because it was excluded for some other reason; neither the user guide nor the API reference provides a method to figure this out.\n\nRobots.txt rules intended to block DeepSeekBot are targeted against a crawler that the Known Agents bot directory describes as being associated with training data. It does not appear from DeepSeek’s initial launch pages if such a rule will affect what is included in DeepSeek’s search index.\n\n## Looking Ahead\n\nIf you use Claude Code, Codex, or DeepSeek Harness with the DeepSeek API, your server-side searches and page fetches are already handled through the Search and Fetch APIs at no cost. Billing for these server-side calls will begin on Oct. 31 at 16:00 UTC (noon ET).\n\nWatch DeepSeek’s docs for a definition of GEO manipulation, details on how tiers are set, and a named crawler for the index.", "url": "https://wpnews.pro/news/deepseek-opens-its-in-house-search-engine-to-developers", "canonical_source": "https://www.searchenginejournal.com/deepseek-opens-its-in-house-search-engine-to-developers/593526/", "published_at": "2026-10-19 15:02:15+00:00", "updated_at": "2026-10-19 15:15:29.669911+00:00", "lang": "en", "topics": ["ai-search", "ai-crawlers", "generative-engine-optimization", "ai-tools", "developer-tools"], "entities": ["DeepSeek", "Bocha", "Google", "Dan Petrovic", "DEJAN", "DeepSeek-V4", "Search API", "Fetch API"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/deepseek-opens-its-in-house-search-engine-to-developers", "markdown": "https://wpnews.pro/news/deepseek-opens-its-in-house-search-engine-to-developers.md", "text": "https://wpnews.pro/news/deepseek-opens-its-in-house-search-engine-to-developers.txt", "jsonld": "https://wpnews.pro/news/deepseek-opens-its-in-house-search-engine-to-developers.jsonld"}}