Verification report details

Is deepseek-v4-flash genuine? Standard check result

Report ID MZZR20260711055913E29787Generated at 2026/07/11 13:59

Highly matched

deepseek-v4-flash 本次标准验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

100Model consistency score

All primary checks passed in this run.

Tested byMozhenzhen
Tested modelDeepSeek V4 Flash
ProvidersDeepSeek API 型号池
Requests25
Duration2 min 30 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。

Token usage check

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

Reported usage1.4MThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation16% 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 rate75.4%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run13.6KCached tokens10.2KNon-cached tokens3.3KAverage per run2.7K
Usage reportedReportedCache billingHappenedResultNormal
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次:缓存占比 0.0%,缓存 0 token,本次用量 2.7K token0.0%1times第 2 次:缓存占比 94.8%,缓存 2.6K token,本次用量 2.7K token94.8%2times第 3 次:缓存占比 93.5%,缓存 2.6K token,本次用量 2.7K token93.5%3times第 4 次:缓存占比 94.9%,缓存 2.6K token,本次用量 2.7K token94.9%4times第 5 次:缓存占比 94.2%,缓存 2.6K token,本次用量 2.7K token94.2%5times
Long-context test

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

7 tiers
Verified up to 1M

All tested context tiers (32K / 64K / 100K / 200K / 400K / 800K / 1M) returned reliably.

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

Results for this test

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

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed15 / 15
No deductions
Does the API respond properly15 / 15
No deductions
Is it the model it claims to be20 / 20
No deductions
Does it answer like the official model20 / 20
No deductions
Is usage and billing reasonable15 / 15
No deductions
Will it keep working15 / 15
No deductions

Test details

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

20 checks
Model list visibility

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

Passed
Test details
This test ran 2 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 267 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 56 tokens
标签结构复述

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

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

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

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

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 64 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 111 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 170 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 184 tokens
连问 5 次,重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 13.6K tokens
of which 10.2K tokens were billed at the cache price
32K 上下文能力实测

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

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

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

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

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

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

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

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

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

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

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 800K
This test used 426.9K tokens
1M 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 1M
This test used 549.8K tokens

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? Standard check result

Report ID:MZZR20260711055913E29787Generated at:2026/07/11 13:59
Provider detailsAI 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

Highly matched

deepseek-v4-flash 本次标准验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

Tested byMozhenzhen
Tested modelDeepSeek V4 Flash
ProvidersDeepSeek API 型号池
Requests25
Duration3 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage1.4MThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation16% 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 rate75.4%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run13.6KCached tokens10.2KNon-cached tokens3.3KAverage per run2.7K
Usage reportedReportedCache billingHappenedResultNormal
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次:缓存占比 0.0%,缓存 0 token,本次用量 2.7K token0.0%1times第 2 次:缓存占比 94.8%,缓存 2.6K token,本次用量 2.7K token94.8%2times第 3 次:缓存占比 93.5%,缓存 2.6K token,本次用量 2.7K token93.5%3times第 4 次:缓存占比 94.9%,缓存 2.6K token,本次用量 2.7K token94.9%4times第 5 次:缓存占比 94.2%,缓存 2.6K token,本次用量 2.7K token94.2%5times
Long-context test

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

7 tiers
Verified up to 1M

All tested context tiers (32K / 64K / 100K / 200K / 400K / 800K / 1M) returned reliably.

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

Results for this test

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

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed15 / 15
No deductions
Does the API respond properly15 / 15
No deductions
Is it the model it claims to be20 / 20
No deductions
Does it answer like the official model20 / 20
No deductions
Is usage and billing reasonable15 / 15
No deductions
Will it keep working15 / 15
No deductions

Test details

Expand any row for details; anything private has been removed

20 checks
Model list visibility

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

Passed
Test details
This test ran 2 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 267 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 56 tokens
标签结构复述

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

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

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

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

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 64 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 111 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 170 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 184 tokens
连问 5 次,重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 13.6K tokens
of which 10.2K tokens were billed at the cache price
32K 上下文能力实测

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

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

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

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

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

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

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

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

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

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

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 800K
This test used 426.9K tokens
1M 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 1M
This test used 549.8K tokens

Reviews

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

发表评论