A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
Identity confirmedModel verified
Confirmed as the official deepseek-v4.1-flash
Behavior matches the official deepseek-v4.1-flash.
Brand consistency97/100
Model match score (deepseek-v4.1-flash)97/100
Checks15/17 Passed
- Providers
- 爱堡云AI
- Claimed model
- deepseek-v4.1-flash
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 18
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidReference108 official models · 2/3 Valid
Answer by answer2 answers: 2 match deepseek-v4.1-flash
Similarity to official modelsTop 5
- deepseek-v4.1-flashClaimed model97%
- claude-opus-4-52%
- qwen3.7-max<1%
- qwen3.7-plus<1%
- grok-4-1-fast-non-reasoning<1%
02Test details
17 items · 15 passed · 2 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes deepseek-v4.1-flash |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 2 / 3 valid | Some samples could not be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the DeepSeek family; brand match score 97 |
| C-03 | Model consistency | Match | 与官方 deepseek-v4.1-flash 吻合，型号一致度 97 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 95% of repeated requests were billed at the cache price. |
| D-02 | Context length | 1M passed | 32K / 128K / 400K / 1M: every tier was read in full. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 429） |
03Which apps can connect
Tried once per app with deepseek-v4.1-flash, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio95.5%
Cache billing works
On average 95% of repeated requests were billed at the cache price.
Usage this run26.9KCached tokens20.5KNon-cached tokens6.4KAverage per run5.4K
Usage reportedReportedCache billingHappenedResultCache billing works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 1M
32K / 128K / 400K / 1M: every tier was read in full.
Reference windowVerified up to 1MThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 27.8K received
- 128KRead in full · 121.9K received
- 400KRead in full · 376.4K received
- 1MRead in full · 923.8K received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage1.5MThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches the estimateFigures are as reported by the API; your bill is authoritative.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Reviews
还没有人评论，来写第一条。
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
deepseek-v4.1-flash verification report
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
Identity confirmedModel verified
Confirmed as the official deepseek-v4.1-flash
Behavior matches the official deepseek-v4.1-flash.
Brand consistency97/100
Model match score (deepseek-v4.1-flash)97/100
Checks15/17 Passed
- Providers
- 爱堡云AI
- Claimed model
- deepseek-v4.1-flash
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 18
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidReference108 official models · 2/3 Valid
Answer by answer2 answers: 2 match deepseek-v4.1-flash
Similarity to official modelsTop 5
- deepseek-v4.1-flashClaimed model97%
- claude-opus-4-52%
- qwen3.7-max<1%
- qwen3.7-plus<1%
- grok-4-1-fast-non-reasoning<1%
02Test details
17 items · 15 passed · 2 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes deepseek-v4.1-flash |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 2 / 3 valid | Some samples could not be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the DeepSeek family; brand match score 97 |
| C-03 | Model consistency | Match | 与官方 deepseek-v4.1-flash 吻合，型号一致度 97 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 95% of repeated requests were billed at the cache price. |
| D-02 | Context length | 1M passed | 32K / 128K / 400K / 1M: every tier was read in full. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 429） |
03Which apps can connect
Tried once per app with deepseek-v4.1-flash, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio95.5%
Cache billing works
On average 95% of repeated requests were billed at the cache price.
Usage this run26.9KCached tokens20.5KNon-cached tokens6.4KAverage per run5.4K
Usage reportedReportedCache billingHappenedResultCache billing works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 1M
32K / 128K / 400K / 1M: every tier was read in full.
Reference windowVerified up to 1MThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 27.8K received
- 128KRead in full · 121.9K received
- 400KRead in full · 376.4K received
- 1MRead in full · 923.8K received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage1.5MThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches the estimateFigures are as reported by the API; your bill is authoritative.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Reviews
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论