The DeepSeek API pricing documentation is updated and defines “peak” and “off-peak” periods. If the API is called during a “peak” period, the cost increases. The dsh-high-fee-alert plugin is designed to monitor the current time, check whether the current time falls within a pricing “peak” period, and alert the user when detected.
Core Features¶
The plugin fetches the latest pricing documentation when DSH starts and obtains Beijing time from ntp.ntsc.ac.cn. When the system detects that it is currently in a “peak” period, it displays a 710×430 alert window in the center of the screen.
The window contains two buttons:
* “OK”: Requests the host to close the DeepSeek Harness process.
* “Continue”: Closes only the current alert window without exiting the process.
The plugin provides two HTTP interfaces for status queries and control:
* GET /dsh-high-fee-alert/status: Query current time, whether it is peak, next off-peak time, etc.
* POST /dsh-high-fee-alert/exit: Request to close the front-end and back-end (requires a same-origin POST).
Installation and Enabling¶
It is recommended to install using npm:
dsh plugin add --profile web dsh-high-fee-alert
It can also be installed from a GitHub repository or a local file:
dsh plugin --profile web add "file:D:/Deepseek Harness/chajian/dsh-high-fee-alert"
After installation, restart DSH to apply it.
Configuration¶
All configuration items are located in the cordis.patch.yml file of the profile, and default values can be overridden by line id. Main configuration items include:
peakWindows: Explicit peak windows (an array of Beijing timeHH:mm-HH:mmstrings).weekdaysOnly: Whether peak periods are limited to Monday through Friday only.pricingUrl: The pricing documentation URL.ntpHost: The NTP server address.
Example configuration (fixed weekday peak from 09:00–18:00):
- id: dsh-high-fee-alert
config:
peakWindows:
- '09:00-12:00'
- '14:00-18:00'
weekdaysOnly: true
Notes¶
- Requires Node.js version >= 20.
- After clicking the “OK” button, the DSH web page may not close automatically; the user must manually close the browser tab (the background process has already exited).
- The author states that there is currently no capacity to maintain updates, and known bugs cannot be fixed.