ByteDance DeepSeek V4.1 Flash review: answers indistinguishable from official, input counts don't match
In the 2026-11-03/04 APB Full run, ByteDance's Q is 42.05, and the 95% interval of its gap to the DeepSeek official channel includes 0. F is 74.98: the APB v2 parameter-contract check failed, and reported input tokens do not match the native count.
On 2026-11-03/04, DeepSeek V4.1 Flash 1017 was tested on six providers through AIHubMix with the APB Full suite, using the same questions, parameters and request scripts for each. This APB Profile covers ByteDance only: what each section measured and how it came out.
The numbers below are scores, not a ranking or a provider recommendation. The four scores, Q, F, P and R, come first; the overall is a summary index, not a certification, and it has no confidence interval. The scoring rules are defined in AIHubMix Provider Benchmark Standard v2.0.
Scores across six providers

| Provider | Q quality | F function | P speed | K cache | R stability | Overall |
|---|---|---|---|---|---|---|
| ByteDance (this post) | 42.05 | 74.98 | 84.37 | 93.83 | 100 | 66.37 |
| Baidu | 38.00 | 88.39 | 37.77 | 68.85 | 100 | 56.48 |
| Alibaba Cloud | 41.75 | 89.78 | 88.58 | 99.37 | 100 | 73.38 |
| DeepSeek official channel | 42.45 | 94.00 | 86.14 | 98.38 | 100 | 73.76 |
| Fireworks | 41.42 | 71.78 | 79.51 | 60.68 | 100 | 64.10 |
| Pareto | 44.58 | 93.42 | 57.69 | 27.58 | 100 | 68.72 |
Providers are listed in a fixed order, not a ranking. K is a sub-score of P, accounting for 20% of it, and is listed separately for reference. The overall score is computed with the composition rules of AIHubMix Provider Benchmark Standard, which also take in the comparison with the official channel and evidence completeness; it is not a direct weighting of the four scores in the table. It is a summary index with no confidence interval. The DeepSeek official channel and Alibaba Cloud differ by only 0.37 overall, which is not a distinguishable difference.
At a glance
- Answer quality: Q 42.05, with BFCL 85.20%, HLE 15.34% and AA-LCR 49.20%. The gap to the official channel is −0.40 percentage points, with a 95% interval of −1.46 to +0.66: not distinguishable. AA-LCR had 28 request failures, all in window 1, counted as wrong.
- Function support: F 74.98; 124 of 174 counted checks passed. The APB v2 parameter-contract check failed; a 10k input was reported as 10,026 tokens (native count 10,000), and an 8-token short input as 34 tokens.
- Response speed: P 84.37. Median first body token 2.12 s at single concurrency and 2.10 s at 10-way, TPOT 3.43 ms; all 180 speed requests were valid.
- Cache: K 93.83. The 8k hot requests hit 9 of 9; 32k hit 8 times, and 1 more had not finished by the 300 s deadline.
- Service stability: R 100. All 300 dedicated requests succeeded on the first attempt.
Test setup
| Item | Detail |
|---|---|
| Model | DeepSeek V4.1 Flash 1017 |
| Requested model ID | doubao-deepseek-v4.1-flash-1017 |
| Returned model name | deepseek-v4-1-flash-261017 |
| Access route | Through AIHubMix with a provider-specific model ID, not a direct connection to the provider's account |
| Parameters | Fixed APB v2 request profile, temperature 1.0, max_tokens 16,384, 300 s timeout, no automatic retry |
| Test profile | The five providers other than Pareto shared one fixed APB v2 profile for Q/P/K/R; F also checked its parameter contract |
| Time | 2026-11-03 18:07 – 11-04 16:33; cache requests 11-04 22:09–23:12; all UTC+8. All six providers shared one Mac mini, one network and one account. |
| Samples | Q 4,250 question-instances; F 180 checks; P 180 requests; R 300; K 30 |
Requests used the AIHubMix quick start route with a provider-specific model ID; the other providers' IDs are listed on the models page. The model's own parameters are described in DeepSeek's API documentation.
Q — answer quality: 42.05
Answer quality draws on three suites: 500 BFCL questions answered 3 times each, 250 HLE questions answered 10 times each, and 25 AA-LCR questions answered 10 times each. BFCL is scored by automatic rules; HLE and AA-LCR are judged right or wrong by the judge model deepseek-flash. All six providers received the same questions, and the three suites are pooled into one accuracy. Ten answers were removed because the question could not be scored, leaving 4,240 scored question-instances.
| Suite | Questions × rounds | Correct | Accuracy | Service failures |
|---|---|---|---|---|
| BFCL tool calls, auto-scored | 500 × 3 | 1,278/1,500 | 85.20% | 0 |
| HLE hard QA, judge-scored | 250 × 10 | 382/2,490 | 15.34% | 7 |
| AA-LCR long-doc reasoning, judge-scored | 25 × 10 | 123/250 | 49.20% | 28 |
| Total · 95% interval 39.70%–44.33% | — | 1,783/4,240 | 42.05% | 35 |
Service failures (failed requests or truncated output) stay in the denominator as wrong answers: HLE output hit the max_tokens ceiling 7 times; AA-LCR had 28 request failures, all in window 1.
| BFCL category | Passed | Pass rate |
|---|---|---|
| simple_python: one function, right call and arguments | 329/360 | 91.39% |
| multiple: pick the right one of several functions | 268/300 | 89.33% |
| parallel: one function called several times at once | 271/300 | 90.33% |
| parallel_multiple: several functions at once | 207/240 | 86.25% |
| irrelevance: no relevant function, so no call | 102/150 | 68.00% |
| ahm_multi_turn: three-stage tool chain | 101/150 | 67.33% |
Each BFCL question was answered 3 times; the table sums the 3 rounds.
Compared with the other five


| Provider | BFCL | HLE | AA-LCR | Combined | Vs official |
|---|---|---|---|---|---|
| ByteDance (this post) | 85.20% | 15.34% | 49.20% | 42.05% | −0.40 (−1.46 to +0.66), not distinguishable |
| Baidu | 86.40% | 9.36% | 32.80% | 38.00% | −4.46 (−5.78 to −3.16), below official |
| Alibaba Cloud | 87.00% | 13.29% | 53.60% | 41.75% | −0.71 (−1.72 to +0.26), not distinguishable |
| DeepSeek official channel | 86.13% | 15.06% | 53.20% | 42.45% | Baseline |
| Fireworks | 85.53% | 14.38% | 46.00% | 41.42% | −1.04 (−2.14 to +0.05), not distinguishable |
| Pareto | 85.27% | 19.32% | 52.00% | 44.58% | +2.12 (−0.02 to +4.18), not distinguishable |
Vs official: the accuracy gap in percentage points, with the 95% interval in brackets; an interval that crosses 0 is recorded as not distinguishable. The HLE and AA-LCR judge, deepseek-flash, belongs to the same DeepSeek family as the tested model and was not calibrated, so its judgments may be lenient.
F — function support: 74.98
The function suite looks only at whether interface behaviour matches the protocol, not at whether the model answers well. Sixty cases in six groups ran once in each of three windows: 180 checks, judged against the format each provider documents. Checks that were not applicable, invalid or unobserved leave the denominator. ByteDance passed 124 of 174 counted checks and scored 74.98 on the group weights.
| Case group | Weight | Passed | Excluded | Group score |
|---|---|---|---|---|
| Streaming and message protocol | 20% | 23/27 | 3 | 85.19 |
| Tool interface | 20% | 30/30 | — | 100.00 |
| Output constraints and parameters | 20% | 24/30 | — | 80.00 |
| Context and state | 15% | 14/30 | — | 46.67 |
| Errors and recovery | 15% | 21/30 | — | 70.00 |
| Metering and cache protocol | 10% | 12/27 | 3 | 44.44 |
| Total · weighted score | — | 124/174 | 6 | 74.98 |
The weighted score applies the group weights; it is not simply passed checks divided by 174.
| Failed case | Windows | Reason |
|---|---|---|
| Reasoning stays out of content · streaming and message protocol | 3/3 | The APB v2 parameter-contract check still returned thinking content |
| Thinking config takes effect · output constraints and parameters | 3/3 | The APB v2 parameter-contract check still returned thinking content |
| Sampling diversity · output constraints and parameters | 3/3 | Outputs at temperature 0 and 1 differed too little for the pre-registered bar |
| 10k long input · context and state | 3/3 | Reported 10,026 input tokens; the native count is 10,000 |
| Within context limit · context and state | 3/3 | Reported 10,026 input tokens; the native count is 10,000 |
| 32k long input · context and state | 3/3 | Reported 10,026 input tokens; the native count is 10,000 |
| 100k long input · context and state | 3/3 | Reported 10,026 input tokens; the native count is 10,000 |
| Over context · context and state | 3/3 | Upstream connection failure or timeout (1); 200 instead of a parameter error (2) |
| 12-turn history · context and state | 1/3 | Upstream connection failure or timeout |
| Malformed messages · errors and recovery | 3/3 | 400 with an empty body, no structured error |
| Orphan tool result · errors and recovery | 3/3 | Returned 200 instead of a parameter error |
| Malformed stream_options · errors and recovery | 3/3 | 400 with an empty body, no structured error |
| Reasoning-token metering · metering and cache protocol | 3/3 | The APB v2 parameter-contract check still reported reasoning tokens |
| Native input count · metering and cache protocol | 3/3 | Reported 34 input tokens; the native count is 8 |
| Tool definitions counted in input · metering and cache protocol | 3/3 | Even the no-tools control misreported input tokens |
| Input count stable with cache · metering and cache protocol | 3/3 | With a repeated prefix, reported input tokens missed the native count |
| Streaming vs non-streaming input · metering and cache protocol | 3/3 | Streaming and non-streaming both reported 34; native count is 8 |
| Exact text output · streaming and message protocol | 1/3 | An extra final period broke the exact-text match |
“Windows” is how many of the 3 windows failed the check.
| Status | Case | Count | Reason |
|---|---|---|---|
| Unobserved | Streaming stop sequence | 3 | The request for this step was not sent after the previous step, so it could not be judged |
| Not applicable | Explicit cache_control | 3 | Registered in advance as unsupported by this interface |
These checks leave the denominator; they count as neither a pass nor a failure.
The malformed-messages and malformed-stream-options error cases failed on several providers: they returned 400 with an empty body, so the client gets no structured error explanation. Reasoning-token metering behaved differently from provider to provider.
Compared with the other five

| Provider | Passed | Failed | Excluded | Weighted score |
|---|---|---|---|---|
| ByteDance (this post) | 124 | 50 | 6 | 74.98 |
| Baidu | 148 | 26 | 6 | 88.39 |
| Alibaba Cloud | 155 | 22 | 3 | 89.78 |
| DeepSeek official channel | 137 | 10 | 33 | 94.00 |
| Fireworks | 122 | 55 | 3 | 71.78 |
| Pareto | 29 | 4 | 147 | 93.42 |
P — response speed: 84.37
Each request carried about 10,000 input tokens and asked for about 1,100 output tokens of body text. In each of three windows, 30 requests ran at single concurrency and 30 at 10-way concurrency: 180 requests in all.
| Item | Detail |
|---|---|
| First body token (TTFA) | Median 2.12 s single, 2.10 s at 10-way |
| Generation speed (TPOT) | 3.43 ms/token single, 3.41 ms/token at 10-way |
| Effective throughput | 1,250.0 token/s at 10-way |
| Valid requests | 90/90 single, 90/90 at 10-way |
| Sub-scores | TTFA 48.59, TPOT 100.00, throughput 100.00; TTFA and TPOT take the lower tier, weighted 35% / 35% / 30%: response score 82.00 |
| P score | Response score 82.00 × 80% + cache K 93.83 × 20% = 84.37 |
TPOT is estimated from streamed chunks, not measured per token on the hardware. Throughput is valid output tokens at 10-way concurrency divided by batch wall-clock time.
Compared with the other five

| Provider | Valid requests | TTFA single | TTFA 10-way | TPOT (slower) | Throughput tok/s | Response |
|---|---|---|---|---|---|---|
| ByteDance (this post) | 180/180 | 2.12 s | 2.10 s | 3.43 ms | 1,250 | 82.00 |
| Baidu | 118/180 | 2.26 s | ∞ | 50.00 ms | 1,329 | 30.00 |
| Alibaba Cloud | 180/180 | 1.34 s | 1.35 s | 4.69 ms | 1,314 | 85.88 |
| DeepSeek official channel | 165/180 | 1.87 s | 1.72 s | 2.84 ms | 1,546 | 83.08 |
| Fireworks | 179/180 | 1.63 s | 1.64 s | 3.29 ms | 1,505 | 84.22 |
| Pareto | 110/180 | 5.85 s | 6.13 s | 4.63 ms | 519 | 65.22 |
All six shared one machine, network and account. The three windows were scheduled provider by provider, so collection periods do not fully overlap; small differences should not be over-read. ∞ means more than half the requests were invalid, so the median counts as infinite.
K — cache: 93.83
Each group sends five requests. The first carries a fixed prefix of about 8k or 32k tokens and seeds the cache. Requests 2–4 keep the prefix and change only the final question, at gaps of 5 s, 30 s and 120 s. The fifth uses a new prefix as a cold control. Three windows × two lengths make 30 requests. K is the cache tokens read by hot requests divided by the tokens that should be reusable under the rules, with the two lengths weighted equally; K is 20% of P.
| Window | 1 · seed | 2 · +5 s | 3 · +30 s | 4 · +120 s | 5 · cold |
|---|---|---|---|---|---|
| 8k prefix · hot hits 9/9 · read 71,424 of 72,261 reusable · 98.84 | — | — | — | — | — |
| Window 1 | 0 | 7,936 | 7,936 | 7,936 | 0 |
| Window 2 | 0 | 7,936 | 7,936 | 7,936 | 0 |
| Window 3 | 0 | 7,936 | 7,936 | 7,936 | 0 |
| 32k prefix · hot hits 8/9 · read 256,000 of 288,270 reusable · 88.81 | — | — | — | — | — |
| Window 1 | 0 | 32,000 | 32,000 | 32,000 | 0 |
| Window 2 | 0 | 32,000 | 32,000 | Failed | 0 |
| Window 3 | 0 | 32,000 | 32,000 | 32,000 | 0 |
| K (8k and 32k weighted equally) | — | — | — | — | 93.83 |
Values are cache-read tokens reported by the server; “Not returned” means the field was absent from the response.
All nine 8k hot requests hit, each reading 7,936 tokens; 8 of 9 32k hot requests hit, each reading 32,000 tokens, and 1 request failed. Cold requests read no cache, so hot and cold separate cleanly. The failed request was the 32k group's 4th request in window 2, which reached the 300 s deadline without completing.
Compared with the other five

| Provider | 8k hits | 8k | 32k hits | 32k | K |
|---|---|---|---|---|---|
| ByteDance (this post) | 9/9 | 98.84 | 8/9 | 88.81 | 93.83 |
| Baidu | 5/9 | 49.60 | 8/9 | 88.10 | 68.85 |
| Alibaba Cloud | 9/9 | 98.83 | 9/9 | 99.90 | 99.37 |
| DeepSeek official channel | 9/9 | 97.25 | 9/9 | 99.51 | 98.38 |
| Fireworks | 3/9 | 32.81 | 8/9 | 88.54 | 60.68 |
| Pareto | 2/9 | 21.89 | 3/9 | 33.27 | 27.58 |
R — service stability: 100
The 300 requests fall into four types: short text, long input, tool calls and multi-turn history. They ran at single concurrency across three windows. Only whether the first attempt returned a valid, complete response is checked; answers are not graded and nothing is retried. Failures in the answer-quality and speed sections are counted in Q and P, not again in R.
| Request type | First-attempt success |
|---|---|
| Short text | 120/120 |
| 10k long input | 90/90 |
| Tool calls | 60/60 |
| Multi-turn history | 30/30 |
| Total · 95% interval 98.78%–100% | 300/300 |
All 300 requests returned a valid, complete response on the first attempt. R = 100 describes these 300 dedicated requests only; it does not mean the whole chain had no failures. The lower bound of the 95% interval is 98.78%: 300 successes out of 300 can only say the failure rate is likely below 1.22%.
Compared with the other five
| Provider | First-attempt success | 95% interval |
|---|---|---|
| ByteDance (this post) | 300/300 | 98.78%–100% |
| Baidu | 300/300 | 98.78%–100% |
| Alibaba Cloud | 300/300 | 98.78%–100% |
| DeepSeek official channel | 300/300 | 98.78%–100% |
| Fireworks | 300/300 | 98.78%–100% |
| Pareto | 300/300 | 98.78%–100% |
R covers only these 300 dedicated requests; failures in the answer-quality and speed sections are recorded in Q and P and are not counted again in R.
FAQ
Why did the APB v2 parameter-contract check fail?
In the separate APB v2 parameter-contract check, ByteDance still returned thinking content and still reported reasoning tokens, so those F cases failed in all three windows. The contract check belongs to F only; Q, P, K and R used one shared request configuration.
BFCL accuracy is 85.20%. Why is Q only 42.05?
Q pools three suites of very different difficulty. BFCL contributed 1,278 correct out of 1,500, HLE 382 out of 2,490 and AA-LCR 123 out of 250. Combined, 1,783 of 4,240 scored question-instances were correct: 42.05%. HLE's 15.34% pulls the pooled figure down.
Are the 35 service failures in Q counted in the score?
Yes. Failed requests and truncated output stay in the denominator and count as wrong. Seven HLE answers were cut off at max_tokens; 28 AA-LCR requests failed, all in window 1.
What do the input-token checks show?
They compare reported input tokens with the model's native count. A 10k input was reported as 10,026 tokens (native 10,000) and an 8-token input as 34. Even the no-tools control misreported, and streaming and non-streaming both reported 34. In the metering and cache protocol group, five checks failed in all three windows.
Was the 32k cache result a miss or a failure?
A failure. Eight of nine 32k hot requests hit and read 32,000 tokens. The other was the 4th request in window 2, which reached the 300 s deadline without completing. The 8k group hit 9 of 9 at 7,936 tokens.
Is ByteDance's answer quality distinguishable from the official channel?
No. Combined accuracy is 0.40 points below the official channel, with a 95% interval of −1.46 to +0.66, which includes 0. This describes this batch only and is not a ranking.
Keep reading: the DeepSeek V4.1 Flash series
- The Q baseline in this post is the official channel; its own run, with F 94.00 and 15 invalid single-concurrency requests, is in DeepSeek official channel DeepSeek V4.1 Flash review: comparison baseline, 15 invalid requests at single concurrency.
- Baidu is the one provider whose Q interval sits below the official channel; the channel failures behind that are in Baidu DeepSeek V4.1 Flash review: tool calling on par with official, frequent no-available-channel pulls down answer quality and speed.
- Alibaba Cloud's 99.37 cache result sits next to the 93.83 reported here: Alibaba Cloud DeepSeek V4.1 Flash review: 1.34s first body token, all 18 hot requests hit cache, answers indistinguishable from official.
- Fireworks shares the parameter-contract and input-count failures seen here, and adds empty stop replies: Fireworks DeepSeek V4.1 Flash review: stop requests return empty body, 8k cache hot requests hit 3 of 9.
- Pareto's 8k and 32k hot requests hit far less often than ByteDance's; its cache and speed results are in Pareto DeepSeek V4.1 Flash review: only 5 hits in 18 hot requests, answers indistinguishable from official.
Sources
- DeepSeek V4.1 Flash 1017 model page (AIHubMix)
- AIHubMix Provider Benchmark Standard v2.0 (AIHubMix docs)
- Quick start (AIHubMix docs)
- Models (AIHubMix)
- DeepSeek API documentation (DeepSeek)