Comparison · DeepSeek and Qwen
DeepSeek V4 Pro 0813 vs Qwen3.8 Max (0902)
Listed API prices of DeepSeek V4 Pro 0813 and Qwen3.8 Max (0902) turned into the cost of the same three standard tasks, with speed from our own test requests in the United States and what each provider’s API documentation says about features that break on a switch. Output quality and answer length are not compared.
Calculated impact cost per task and per month
For an L2 task (deep analysis over a 50,000-token document, 3 steps), DeepSeek V4 Pro 0813 costs $0.222 and Qwen3.8 Max (0902) $0.336 at the prices listed in the United States on , so DeepSeek V4 Pro 0813 is 34.0 % less than Qwen3.8 Max (0902), counting visible output only, without cache discounts or hidden reasoning.
| Task | DeepSeek V4 Pro 0813, per task | Qwen3.8 Max (0902), per task | DeepSeek V4 Pro 0813, per month | Qwen3.8 Max (0902), per month | DeepSeek V4 Pro 0813 vs Qwen3.8 Max (0902), per task |
|---|---|---|---|---|---|
| L1Micro-task (classification or strict JSON extraction) | $0.0028per L1 task | $0.0042per L1 task | $40.47per month | $61.32per month | −34.0 % |
| L2Deep analysis over a 50,000-token document | $0.222per L2 task | $0.336per L2 task | $3,237.70per month | $4,905.60per month | −34.0 % |
| L3Agentic coding loop, 15 steps | $1.77per L3 task | $2.69per L3 task | $25,872.66per month | $39,201.00per month | −34.0 % |
Calculated Per month: 20 tasks an hour around the clock, 730 hours.
Prices USD per 1M tokens
| Price | DeepSeek V4 Pro 0813 | Qwen3.8 Max (0902) |
|---|---|---|
| Input, per 1M tokens | $1.32 | $2.00 |
| Output, per 1M tokens | $3.96 | $6.00 |
| Price from | Provider's price list · source page Published | Provider's price list · source page Published |
| Read | · the United States | · the United States |
| Context window | 1,048,576 tokens | 1,000,000 tokens |
What can I use it for? six common tasks, our data checks
Quality on your task: not measured by Measured Lab yet.
| Task | DeepSeek V4 Pro 0813 | Qwen3.8 Max (0902) |
|---|---|---|
| Answer customer messages | Fits on price and context | Fits on price and context |
| Pull data from invoices and documents with strict JSON and page images | Not confirmed: reads text only, per the OpenRouter listing; strict JSON output partly, per DeepSeek’s documentation | Fits on price and context |
| Summarize documents and meetings | Fits on price and context | Fits on price and context |
| Translate content | Fits on price and context | Fits on price and context |
| Chat assistant on your website | Fits on price and context | Fits on price and context |
| Write and review code with tool calls | Fits on price and context | Fits on price and context |
| Tasks it fits | 5 of 6 | 6 of 6 |
Checks of our data for six common tasks: a published price, a context window and answer length for the task and, where the task needs them, strict JSON output, page images and tool calls; prices, cost a month and terms for each model on its model card. Compare models for your own task in the model picker.
Speed in the US Observed our test requests
In our test requests from the United States, the median time to the first answer token was 984 ms for DeepSeek V4 Pro 0813 (Direct API · DeepSeek) and 1,504 ms for Qwen3.8 Max (0902) (Direct API · Alibaba Cloud).
| Model and route | Time to first answer token, median | Output speed, median | Answers |
|---|---|---|---|
| DeepSeek V4 Pro 0813Direct API · DeepSeek | 984 ms range 527 ms–1,480 ms | 75.5 tokens/s range 38.4 tokens/s–130 tokens/s | 115 answers on 23 dates |
| DeepSeek V4 Pro 0813Hosted by BytePlus | 1,865 ms range 1,309 ms–3,072 ms | 57.5 tokens/s range 45.0 tokens/s–74.0 tokens/s | 110 answers on 22 dates |
| Qwen3.8 Max (0902)Direct API · Alibaba Cloud | 1,504 ms range 1,113 ms–3,190 ms | 43.2 tokens/s range 24.5 tokens/s–59.9 tokens/s | 110 answers on 22 dates |
The same short request to every model, sent from a measurement point in the United States; medians of successful answers on at least 2 different dates, latest on . How we measure
What breaks when you switch Published provider documentation
Moving from DeepSeek to Qwen: every feature that DeepSeek’s documentation lists as supported is also listed as supported by Qwen.
Moving from Qwen to DeepSeek, 1 of the 5 features may not carry over, by each provider’s documentation:
- Parallel tool calls — Qwen: yes; DeepSeek: not stated. An agent built around several calls per turn gets one call per turn: more round trips, more input tokens, slower runs.
| Feature of the API | DeepSeek | Qwen |
|---|---|---|
| Strict JSON schemas | Partly | Partly |
| Parallel tool calls | Not stated | Yes |
| Streamed tool arguments | Not stated | Not stated |
| Reasoning with tools | Yes | Yes |
| Cache covers tool definitions | Not stated | Not stated |
What each provider’s own API documentation says, read ; “not stated” is not the same as “no”. Quotes and sources: what breaks when you switch AI APIs.