Skip to content

guides: DeepSeek Search and Fetch free window ends 2026-11-01 - #146

Merged
WhiteWorld merged 1 commit into
mainfrom
cursor/deepseek-search-fetch-free-window-7ede
Oct 23, 2026
Merged

WhiteWorld merged 1 commit into
mainfrom
cursor/deepseek-search-fetch-free-window-7ede

Conversation

@WhiteWorld

Copy link
Copy Markdown
Owner

What changed

Bilingual howto guide for the DeepSeek Search and Fetch billing cutoff. Frontmatter draft: false so it publishes when this PR merges. The PR itself is a draft for Bai to review.

  • src/content/guides/deepseek-search-fetch-free-window.md
  • src/content/guides-en/deepseek-search-fetch-free-window.md
  • One sentence on the existing API platforms guide (zh + en) pointing at the new page. No other rewrite of the deepseek-* guides.

Guides are picked up by the content collection. Build lists both routes, both RSS feeds, and the sitemap. Related cards on the new page are Harness intro, API platforms, and the vision guide.

The article states there was no live API call and no console screenshot. Counts in the budget section are arithmetic from the published per-1,000 rate, not measured usage.

Evidence opened 2026-10-23 (Asia/Shanghai)

Open questions for Bai

  1. Is the Harness switch Use the new Web Search API inside the free window, or is that direct /v1/tools/* call billed now? The pricing note names products, not plugin ids deepseek-search-api / deepseek-fetch-api. The article tells readers to budget as if it may already be billed.
  2. A given account: 5元 or $0.75? Both are official, on different language pages. This guide does not convert them.
  3. Claude Code and Codex: no off switch found on the integration pages. Is there one elsewhere?
  4. Responses API says deepseek-flash ignores web_search. The Claude Code page does not say Web Search is Pro-only, and its sample uses deepseek-flash. Do flash sessions in Claude Code still emit Search calls?
  5. The API platforms guide still says the official page lists USD only and has no CNY price. That sentence is from the 2026-10-18 check. The Chinese pricing page opened today lists yuan, including Search and Fetch at 5元. Left unchanged except for the cross-link. Worth a separate correction?
  6. Shipped Harness "local HTTP fetch" provider id is not named in the README. @deepseek-ai/dsh-web-fetch-http exists. Whether it is the shipped selection is marked unknown.
  7. No live usage. If you want a measured baseline, that needs an account and a logged run.
Open in Web Open in Cursor 

Document the 2026-11-01 00:00 Beijing cutoff for server-side Search and Fetch in Harness, Claude Code, and Codex, with the standalone API rates and a pre-cutoff log checklist. Link it from the API platforms guide.

Co-authored-by: Liu <ljq258@gmail.com>
@vercel

vercel Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
codepick Ready Ready Preview Oct 23, 2026 12:23am UTC

@WhiteWorld
WhiteWorld marked this pull request as ready for review October 23, 2026 01:02
@WhiteWorld
WhiteWorld merged commit 3465dd7 into main Oct 23, 2026
3 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T01:05:02.167915Z 83f4cbc Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 83f4cbcd8b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

1. The model-facing Harness tool `web_search` takes `queries`, from 1 to 4. The web subsystem doc says each query is fanned out into its own search. One tool call can become several searches. A one-item array is one search.
2. The shipped Messages search provider id is `deepseek-official`, package `@deepseek-ai/dsh-web-search-deepseek`. The README says one search is a full Messages model turn, with up to `maxUses` server-side web searches inside that request. The default is **5**. If all 5 succeed and each one is a billable Search request, the Search fee is `5 / 1000 × unit price`. The README does not say every search hits 5, and it does not say every one returns a non-empty result. That path also spends model tokens.

The 4 on `queries` and the 5 on `maxUses` are two caps. Multiplying them into 20 successful requests is not in the docs. The bill follows the successful-request count. Log that count before the cutoff.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Account for all queries in the Harness search ceiling

At the pinned Harness revision, packages/web/tool-web/src/search.ts::runSearchQueries calls ctx.web.search once for each of the up-to-four queries, while the web-search-deepseek README allows up to maxUses = 5 server-side searches in each resulting Messages request. The documented worst case for deepseek-official is therefore 4 × 5 = 20 server-side searches per model-facing call; saying there is no basis for multiplying these limits understates the post-cutoff cost ceiling by up to 4×. Keep the caveat that actual billing depends on successful searches, but present 20 as the theoretical maximum.

Useful? React with 👍 / 👎.

This branch was successfully deployed

1 active deployment
Preview — 83f4cbcd Deployed Oct 23, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants