2026-11-05 18:17 UTC · deepseek/rate-limit · live page
Summary by fallback. It may be wrong; the diff below is what actually changed. Raw: d31b54adb0-deepseek-rate-limit.diff · commit d31b54adb0
diff --git a/snapshots/deepseek/rate-limit.md b/snapshots/deepseek/rate-limit.mdindex 2a4b0ed..98f056f 100644--- a/snapshots/deepseek/rate-limit.md+++ b/snapshots/deepseek/rate-limit.md@@ -23,5 +23,5 @@ You can pass the `user_id` parameter to the API to achieve fine-grained manageme - For API users with increased concurrency quotas, we will limit the total concurrency under your account, and we will also impose concurrency limits on each `user_id` you pass (an empty id is treated as a special `user_id`). For each `user_id`, the concurrency limit for `deepseek-flash` is 2500, and for `deepseek-v4-pro` it is 500. If a `user_id` exceeds its limit, requests with that `user_id` under your account will receive an HTTP 429 error code -The `user_id` parameter must be a string matching the regex `[a-zA-Z0-9\-_]+`, with a maximum length of 512. Do not include user privacy information in `user_id`.+The `user_id` parameter is a string. We recommend using only ASCII letters, digits, underscores (`_`), and hyphens (`-`). The UTF-8 encoded value must not exceed 512 bytes. Do not include user privacy information in `user_id`. You can set the `user_id` parameter in the following ways: