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 consistency96/100
Model match score (deepseek-v4.1-flash)96/100
Checks12/17 Passed
- Providers
- a6api
- Claimed model
- deepseek-v4.1-flash
- Plan
- Full check
- Reference
- 105 official models
- Requests
- 18
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference105 official models · 6/6 Valid
Answer by answer6 answers: 4 match deepseek-v4.1-flash；another 2 match no model clearly on their own
Similarity to official modelsTop 5
- deepseek-v4.1-flashClaimed model96%
- gpt-6-astra2%
- gpt-6-sol1%
- qwen3.8-max<1%
- gpt-6.1-sol<1%
02Test details
17 items · 12 passed · 5 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 | 6 / 6 valid | 首轮未能判定，已追加一轮；独立采样均可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the DeepSeek family; brand match score 96 |
| C-03 | Model consistency | Match | 与官方 deepseek-v4.1-flash 吻合，型号一致度 96 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 49% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 503. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 503） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 503） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 502） |
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 ratio48.9%
Partly works
On average 49% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run47.2KCached tokens20.5KNon-cached tokens26.8KAverage per run9.4K
Usage reportedReportedCache billingHappenedResultPartly 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.
Boundary at 32K
32K failed: 接口返回 HTTP 503.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 503
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage83.8KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-302.3KEstimated from this test's requests.Deviation47% belowThe reported usage is below the estimate, possibly because of how tokens are counted or compressed.Usage checkBelow 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 consistency96/100
Model match score (deepseek-v4.1-flash)96/100
Checks12/17 Passed
- Providers
- a6api
- Claimed model
- deepseek-v4.1-flash
- Plan
- Full check
- Reference
- 105 official models
- Requests
- 18
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference105 official models · 6/6 Valid
Answer by answer6 answers: 4 match deepseek-v4.1-flash；another 2 match no model clearly on their own
Similarity to official modelsTop 5
- deepseek-v4.1-flashClaimed model96%
- gpt-6-astra2%
- gpt-6-sol1%
- qwen3.8-max<1%
- gpt-6.1-sol<1%
02Test details
17 items · 12 passed · 5 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 | 6 / 6 valid | 首轮未能判定，已追加一轮；独立采样均可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the DeepSeek family; brand match score 96 |
| C-03 | Model consistency | Match | 与官方 deepseek-v4.1-flash 吻合，型号一致度 96 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 49% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 503. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 503） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 503） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 502） |
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 ratio48.9%
Partly works
On average 49% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run47.2KCached tokens20.5KNon-cached tokens26.8KAverage per run9.4K
Usage reportedReportedCache billingHappenedResultPartly 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.
Boundary at 32K
32K failed: 接口返回 HTTP 503.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 503
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage83.8KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-302.3KEstimated from this test's requests.Deviation47% belowThe reported usage is below the estimate, possibly because of how tokens are counted or compressed.Usage checkBelow 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
还没有人评论，来写第一条。
发表评论