2026-09-19 19:51 UTC · deepseek/rate-limit · live page
Summary by fallback. It may be wrong; the diff below is what actually changed. Raw: c694240213-deepseek-rate-limit.diff · commit c694240213
diff --git a/snapshots/deepseek/rate-limit.md b/snapshots/deepseek/rate-limit.mdindex a73d40a..a3b5d42 100644--- a/snapshots/deepseek/rate-limit.md+++ b/snapshots/deepseek/rate-limit.md@@ -7,7 +7,7 @@ For each account, the concurrency limits for different DeepSeek API models are s 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 | deepseek-v4-flash-vision-exp |-|---|---|---|---|-| Concurrency Limit | 500 | 2500 | 2500 |+| | deepseek-flash | deepseek-v4-pro |+|---|---|---|+| Concurrency Limit | 2500 | 500 | - A request counts as one concurrent connection from the time it is sent until the model response is complete@@ -21,5 +21,5 @@ You can pass the `user_id` parameter to the API to achieve fine-grained manageme - 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, for deepseek-v4-flash is 2500, and for deepseek-v4-flash-vision-exp is 2500. If a `user_id` exceeds its limit, requests with that `user_id` under your account will receive an HTTP 429 error code+ - 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`.@@ -30,5 +30,5 @@ HTTP request body: ```-{ "model": "deepseek-v4-pro", "messages": {"role": "user", "content": "Hello!"}, "user_id": "your_user_id"}+{ "model": "deepseek-flash", "messages": {"role": "user", "content": "Hello!"}, "user_id": "your_user_id"} ``` @@ -36,5 +36,5 @@ If you are using the OpenAI SDK, you need to place the `user_id` parameter under ```-response = client.chat.completions.create( model="deepseek-v4-pro", messages=[{"role": "user", "content": "Hello!"}], extra_body={"user_id": "your_user_id"})+response = client.chat.completions.create( model="deepseek-flash", messages=[{"role": "user", "content": "Hello!"}], extra_body={"user_id": "your_user_id"}) ``` @@ -42,5 +42,5 @@ HTTP request body: ```-{ "model": "deepseek-v4-pro", "messages": {"role": "user", "content": "Hello!"}, "metadata": {"user_id": "your_user_id"}, "max_tokens": 1024}+{ "model": "deepseek-flash", "messages": {"role": "user", "content": "Hello!"}, "metadata": {"user_id": "your_user_id"}, "max_tokens": 1024} ``` @@ -48,5 +48,5 @@ 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)+message = client.messages.create( model="deepseek-flash", messages=[{"role": "user", "type": "text", "content": "Hello!"}], metadata={"user_id": "your_user_id"}, max_tokens=1024) ```