A newer report is availableThis report has been superseded by a later retest. View the latest report。
UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency3/100
Model match score (deepseek-v4.1-flash)2/100
Checks11/17 Passed
- Providers
- corealgos
- Claimed model
- deepseek-v4.1-flash
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 15
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidReference101 official models · 2/3 Valid
Answer by answer2 answers: 0 match deepseek-v4.1-flash；another 2 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- claude-opus-4-724%
- claude-opus-4-818%
- mimo-v2.6-flash9%
- claude-sonnet-56%
- hy4-preview4%
02Test details
17 items · 11 passed · 6 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 | Pending review | Brand match score 3; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 2; below the decision threshold |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 76% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 429. |
| 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 | Supported | Returned in the required JSON structure |
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 ratio75.8%
Partly works
On average 76% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run16.3KCached tokens8.2KNon-cached tokens8.1KAverage per run3.3K
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 429.
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 429
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage26.2KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation98% 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.
Post an anonymous comment
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 report is availableThis report has been superseded by a later retest. View the latest report。
UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency3/100
Model match score (deepseek-v4.1-flash)2/100
Checks11/17 Passed
- Providers
- corealgos
- Claimed model
- deepseek-v4.1-flash
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 15
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidReference101 official models · 2/3 Valid
Answer by answer2 answers: 0 match deepseek-v4.1-flash；another 2 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- claude-opus-4-724%
- claude-opus-4-818%
- mimo-v2.6-flash9%
- claude-sonnet-56%
- hy4-preview4%
02Test details
17 items · 11 passed · 6 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 | Pending review | Brand match score 3; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 2; below the decision threshold |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 76% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 429. |
| 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 | Supported | Returned in the required JSON structure |
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 ratio75.8%
Partly works
On average 76% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run16.3KCached tokens8.2KNon-cached tokens8.1KAverage per run3.3K
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 429.
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 429
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage26.2KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation98% 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.