Is deepseek-v4.1-flash genuine? Standard check result

Report ID MZZR2026091803441627281AGenerated at 2026/09/18 11:44

Insufficient evidence to determine

Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.

Insufficient evidenceEvidence status

主要问题：让它按固定格式输出，它做不稳。

Tested byMozhenzhen

Tested modelDeepSeek V4.1 Flash

Providersd1api.xin

Requests21

Duration47 sec

Identity verdictInsufficient evidence to determine

ReferenceReference samples are not sufficiently calibrated

API and capability checks

The basic API call succeeded and returned a recognizable response.

让它按指定格式输出，格式兑现了吗：Needs review
连问 5 次，重复内容有没有按缓存价计费：Needs review

API results and model identity are assessed separately. Insufficient evidence does not mean a failed request or a fake model.

Model reference evidence

The available reference cannot establish model identity. Review the API and capability results for this test.

Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.

Rule version：2026-09-14.v1

Token usage check

Reported usage is used; estimates appear only when none is reported.

Reported usage32.3KThe actual usage reported by the API; this page goes by it.Estimated usage76.7KEstimated from this test's requests.Deviation58% 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.

Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request

Share billed at the cache rate0.0%

No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run13.4KCached tokens0Non-cached tokens13.4KAverage per run2.7K

Usage reportedReportedCache billingDid not happenResultNeeds attention

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

Long-context test

We test how much it can read at once, then compare that with the officially stated length.

1 tiers

Verified up to 32K

All tested context tiers (32K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests begin at the longest generated context and step down to verify stable, correct responses.

Test details

Expand any row for details; anything private has been removed.

17 checks

Model list visibility

deepseek-v4.1-flash is visible in the API model list.

Passed

Test details

This test ran 1 times; result: Passed.

Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed

Test details

This test ran 1 times; result: Passed.

Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 127 tokens

指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 24 tokens

JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 32 tokens

标签结构复述

按官方接口的标准调用，看返回是否规范。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 78 tokens

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 50 tokens

品牌边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 75 tokens

用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 38 tokens

DeepSeek 推理边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 90 tokens

模型代码锚定

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 119 tokens

Model-family test: series and tier identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 93 tokens

边打字边回和一次性回，结果一样吗

对照官方公开的产品说明来测。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 26 tokens

让它调用工具，返回格式对不对

对照官方公开的产品说明来测。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 358 tokens

让它按指定格式输出，格式兑现了吗

对照官方公开的产品说明来测。 1 次里对了 0 次。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Structured output was unstable
This test used 186 tokens

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次里对了 5 次。

Needs review

Test details

This test ran 5 times: 5 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 13.4K tokens

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 17.6K tokens

Post an anonymous comment

Rating

5 points

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is deepseek-v4.1-flash genuine? Standard check result

Report ID:MZZR2026091803441627281AGenerated at：2026/09/18 11:44

Provider details AI model details

Evidence status

Insufficient evidence to determine

Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.

Tested byMozhenzhen

Tested modelDeepSeek V4.1 Flash

Providersd1api.xin

Requests21

Duration47 sec

Identity verdictInsufficient evidence to determine

ReferenceReference samples are not sufficiently calibrated

API and capability checks

The basic API call succeeded and returned a recognizable response.

让它按指定格式输出，格式兑现了吗：Needs review
连问 5 次，重复内容有没有按缓存价计费：Needs review

API results and model identity are assessed separately. Insufficient evidence does not mean a failed request or a fake model.

Model reference evidence

The available reference cannot establish model identity. Review the API and capability results for this test.

Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.

Rule version：2026-09-14.v1

Token usage check

Reported usage is used; estimates appear only when none is reported.

Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request

Share billed at the cache rate0.0%

No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run13.4KCached tokens0Non-cached tokens13.4KAverage per run2.7K

Usage reportedReportedCache billingDid not happenResultNeeds attention

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

Long-context test

We test how much it can read at once, then compare that with the officially stated length.

1 tiers

Verified up to 32K

All tested context tiers (32K) returned reliably.

Test details

Expand any row for details; anything private has been removed

17 checks

Model list visibility

deepseek-v4.1-flash is visible in the API model list.

Passed

Test details

This test ran 1 times; result: Passed.

Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed

Test details

This test ran 1 times; result: Passed.

Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 127 tokens

指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 24 tokens

JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 32 tokens

标签结构复述

按官方接口的标准调用，看返回是否规范。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 78 tokens

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 50 tokens

品牌边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 75 tokens

用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 38 tokens

DeepSeek 推理边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 90 tokens

模型代码锚定

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 119 tokens

Model-family test: series and tier identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 93 tokens

边打字边回和一次性回，结果一样吗

对照官方公开的产品说明来测。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 26 tokens

让它调用工具，返回格式对不对

对照官方公开的产品说明来测。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 358 tokens

让它按指定格式输出，格式兑现了吗

对照官方公开的产品说明来测。 1 次里对了 0 次。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Structured output was unstable
This test used 186 tokens

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次里对了 5 次。

Needs review

Test details

This test ran 5 times: 5 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 13.4K tokens

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 17.6K tokens

Comments and feedback on this report

Rating

5 points