DeepSeek API now sets concurrency limits at 500 for deepseek-v4-pro and 2500 for deepseek-v4-flash, with optional capacity expansion and user_id isolation.

Summary by gemma-4-12b. It may be wrong; the diff below is what actually changed. Raw: de74c44dec-deepseek-rate-limit.diff · commit de74c44dec
diff --git a/snapshots/deepseek/rate-limit.md b/snapshots/deepseek/rate-limit.mdindex d83c91a..7dd595f 100644--- a/snapshots/deepseek/rate-limit.md+++ b/snapshots/deepseek/rate-limit.md@@ -1,9 +1,55 @@ <!-- fineprint snapshot: deepseek/rate-limit | source: https://api-docs.deepseek.com/quick_start/rate_limit --> -# Rate Limit+# Rate Limit & Isolation -DeepSeek API dynamically limits user concurrency based on server load. When you reach the concurrency limit, you will immediately receive an HTTP 429 response.+For each account, the concurrency limits for different DeepSeek API models are shown in the table below. -After your request is sent, it may take some time to receive a response from the server. During this period, your HTTP request will remain connected, and you may continuously receive contents in the following formats:+If you need higher concurrency, you can submit a capacity expansion request. We will match the appropriate concurrency based on your actual business needs. There is no additional cost for capacity expansion.++|  | deepseek-v4-pro | deepseek-v4-flash |+|---|---|---|+| Concurrency Limit | 500 | 2500 |++- A request counts as one concurrent connection from the time it is sent until the model response is complete+- Concurrency limits are calculated at the account level, regardless of which API Key is used+- For a given account, API requests within the concurrency limit will receive a response; when the concurrency limit is exceeded, you will receive an HTTP 429 error code++You can pass the `user_id` parameter to the API to achieve fine-grained management of different users on your business side under the same account. The specific functions of `user_id` are as follows:++- Content Safety Isolation: `user_id` is used to distinguish user identities on your business side for content safety handling+- KVCache Isolation: `user_id` is used to isolate KVCache for users on your business side for privacy management+- Scheduling Isolation: `user_id` is used for scheduling isolation of users on your business side+  - For regular API users, all `user_id` values are combined for concurrency limit calculation+  - 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-v4-pro is 500, and for deepseek-v4-flash is 2500. 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`.++You can set the `user_id` parameter in the following ways:++HTTP request body:++```+{    "model": "deepseek-v4-pro",    "messages": {"role": "user", "content": "Hello!"},    "user_id": "your_user_id"}+```++If you are using the OpenAI SDK, you need to place the `user_id` parameter under the `extra_body` parameter:++```+response = client.chat.completions.create(    model="deepseek-v4-pro",    messages=[{"role": "user", "content": "Hello!"}],    extra_body={"user_id": "your_user_id"})+```++HTTP request body:++```+{    "model": "deepseek-v4-pro",    "messages": {"role": "user", "content": "Hello!"},    "metadata": {"user_id": "your_user_id"},    "max_tokens": 1024}+```++If you are using the Anthropic SDK, the calling method is as follows:++```+message = client.messages.create(    model="deepseek-v4-pro",    messages=[{"role": "user", "type": "text", "content": "Hello!"}],    metadata={"user_id": "your_user_id"},    max_tokens=1024)+```++After your request is sent, it may sometimes take a while to receive a response from the server. During this period, your HTTP request will remain connected, and you may continuously receive contents in the following formats:  - Non-streaming requests: Continuously return empty lines
← DeepSeek timeline