Verification report details

Is deepseek-v4-flash genuine? Deep check result

Report ID MZZR20260808160415E7AF74Generated at 2026/08/09 00:04

Matched

deepseek-v4-flash 本次深度验真结果:Matched(94/100)。主要问题:有个别项需要再复核;看不到缓存用量,享受不到缓存优惠也查不出来。

94Model consistency score

主要问题:有个别项需要再复核;看不到缓存用量,享受不到缓存优惠也查不出来。

Tested byMozhenzhen
Tested modelDeepSeek V4 Flash
Providers308422.xyz
Requests34
Duration3 min 54 sec
Identity verdictVerified
ReferenceOken

Token usage check

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

Reported usage218.4KThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation87% 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.
Long-context test

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

5 tiers
Verified up to 200K

400K 需要关注,原因:上下文保持较弱。

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200K / 400KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

The 400K tier did not return reliably this time; do not rely on this length.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched94/100

主要问题:有个别项需要再复核;看不到缓存用量,享受不到缓存优惠也查不出来。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly12 / 12
No deductions
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model25 / 25
No deductions
Is usage and billing reasonable8 / 10
看不到缓存用量,享受不到缓存优惠也查不出来(连问 5 次,重复内容有没有按缓存价计费) -2
Will it keep working21 / 25
存在需复核项 -4

Test details

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

22 checks
Model list visibility

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

Passed
Test details
This test ran 8 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 106 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 36 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 44 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 85 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 60 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 89 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 50 tokens
逻辑网格推理

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 203 tokens
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。

Passed
Test details
This test ran 2 times: 2 passed.
This test used 86 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 97 tokens
DeepSeek 推理边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 387 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 114 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 97 tokens
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 138 tokens
连问 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 16.7K tokens
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 33.3K tokens
100K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 100K
This test used 51.2K tokens
200K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 200K
This test used 102.3K tokens
400K 上下文能力实测

400K 长度的内容没能稳定读完,这次就记到这里为止。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 400K

Reviews

还没有人评论,来写第一条。

发表评论

MozhenzhenBefore you buy AI, check Mozhenzhen
Scan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls

Is deepseek-v4-flash genuine? Deep check result

Report ID:MZZR20260808160415E7AF74Generated at:2026/08/09 00:04
Provider detailsAI model details
Model consistency score

Matched

deepseek-v4-flash 本次深度验真结果:Matched(94/100)。主要问题:有个别项需要再复核;看不到缓存用量,享受不到缓存优惠也查不出来。

Tested byMozhenzhen
Tested modelDeepSeek V4 Flash
Providers308422.xyz
Requests34
Duration4 min
Identity verdictVerified
ReferenceOken

Token usage check

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

Reported usage218.4KThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation87% 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.
Long-context test

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

5 tiers
Verified up to 200K

400K 需要关注,原因:上下文保持较弱。

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200K / 400KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

The 400K tier did not return reliably this time; do not rely on this length.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched94/100

主要问题:有个别项需要再复核;看不到缓存用量,享受不到缓存优惠也查不出来。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly12 / 12
No deductions
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model25 / 25
No deductions
Is usage and billing reasonable8 / 10
看不到缓存用量,享受不到缓存优惠也查不出来(连问 5 次,重复内容有没有按缓存价计费) -2
Will it keep working21 / 25
存在需复核项 -4

Test details

Expand any row for details; anything private has been removed

22 checks
Model list visibility

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

Passed
Test details
This test ran 8 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 106 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 36 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 44 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 85 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 60 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 89 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 50 tokens
逻辑网格推理

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 203 tokens
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。

Passed
Test details
This test ran 2 times: 2 passed.
This test used 86 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 97 tokens
DeepSeek 推理边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 387 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 114 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 97 tokens
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 138 tokens
连问 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 16.7K tokens
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 33.3K tokens
100K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 100K
This test used 51.2K tokens
200K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 200K
This test used 102.3K tokens
400K 上下文能力实测

400K 长度的内容没能稳定读完,这次就记到这里为止。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 400K

Reviews

还没有人评论,来写第一条。

发表评论