Is deepseek-v4-flash genuine? Deep check result

Report ID MZZR20260708074256EF43F3Generated at 2026/07/08 15:42

Matched with issues

deepseek-v4-flash 本次深度验真结果：Matched但Matched with issues（84/100）。主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

84Model consistency score

主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

Tested byMozhenzhen

Tested modelDeepSeek V4 Flash

ProvidersConeverse AI

Requests107

Duration8 min 33 sec

Identity verdictVerified

ReferenceMozhenzhen's own test standard

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。

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

Token usage check

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

Reported usage918The actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation100% 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 rate--

No usage record

This provider's endpoint does not report usage reliably; check it against your bill.

Usage this run0Cached tokens0Non-cached tokens0Average per run0

Usage reportedNot reportedCache billingDid not happenResult不可观测

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

Boundary at 32K

32K 需要关注，原因：接口服务异常。

Reference windowReference window 1MModel-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.

Current guidance

The 32K 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

Matched with issues84/100

主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly8 / 12

这家的接口当时有故障（逻辑网格推理、复测一致性） -4

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 reasonable10 / 10

No deductions

Will it keep working13 / 25

这家的接口当时有故障（逻辑网格推理、复测一致性） -8有几个关键检测项需要复核 -4

Test details

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

18 checks

Model list visibility

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

Passed

Test details

This test ran 85 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 165 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 137 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 120 tokens

用量数据是否完整

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

Passed

Test details

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

逻辑网格推理

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。有几次没对上。

Needs review

Test details

This test ran 2 times: 2 need attention.
Why it failed: API service error

DeepSeek 推理边界

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

DeepSeek 推理边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

模型代码锚定

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

Deep model test: family-specific boundary

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

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

针对这个模型再做一项专门检测。有几次没对上。

Needs review

Test details

This test ran 5 times: 5 need attention.
Why it failed: API service error

32K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 32K

Reviews

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

发表评论

Before 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:MZZR20260708074256EF43F3Generated at：2026/07/08 15:42

Provider details AI model details

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。

Model consistency score

Matched with issues

deepseek-v4-flash 本次深度验真结果：Matched但Matched with issues（84/100）。主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

Tested byMozhenzhen

Tested modelDeepSeek V4 Flash

ProvidersConeverse AI

Requests107

Duration9 min

Identity verdictVerified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

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 rate--

No usage record

This provider's endpoint does not report usage reliably; check it against your bill.

Usage this run0Cached tokens0Non-cached tokens0Average per run0

Usage reportedNot reportedCache billingDid not happenResult不可观测

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

Boundary at 32K

32K 需要关注，原因：接口服务异常。

Current guidance

The 32K 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

Matched with issues84/100

主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly8 / 12

这家的接口当时有故障（逻辑网格推理、复测一致性） -4

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 reasonable10 / 10

No deductions

Will it keep working13 / 25

这家的接口当时有故障（逻辑网格推理、复测一致性） -8有几个关键检测项需要复核 -4

Test details

Expand any row for details; anything private has been removed

18 checks

Model list visibility

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

Passed

Test details

This test ran 85 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 165 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 137 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 120 tokens

用量数据是否完整

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

Passed

Test details

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

逻辑网格推理

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。有几次没对上。

Needs review

Test details

This test ran 2 times: 2 need attention.
Why it failed: API service error

DeepSeek 推理边界

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

DeepSeek 推理边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

模型代码锚定

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

Deep model test: family-specific boundary

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

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

针对这个模型再做一项专门检测。有几次没对上。

Needs review

Test details

This test ran 5 times: 5 need attention.
Why it failed: API service error

32K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 32K

Reviews

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