Is deepseek-v4-pro-0813 genuine? Standard check result

Report ID MZZR202608271038385EE13DGenerated at 2026/08/27 18:38

Matched

deepseek-v4-pro-0813 本次标准验真结果：Matched（94/100）。主要问题：会含糊地把自己说成官方原厂；有个别项需要再复核。

94Model consistency score

主要问题：会含糊地把自己说成官方原厂；有个别项需要再复核。

Tested byMozhenzhen

Tested modelDeepSeek V4 Pro

Providersa6api

Requests24

Duration4 min 16 sec

Identity verdictVerified

Reference模真真既有版本化基线

Token usage check

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

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

Low cache share

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

Usage this run14.1KCached tokens8.1KNon-cached tokens6.0KAverage per run2.8K

Usage reportedReportedCache billingHappenedResultNormal

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.

7 tiers

Verified up to 32K

1M 需要关注，原因：上下文保持较弱。

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

Current guidance

The 64K 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 listed15 / 15

No deductions

Does the API respond properly15 / 15

No deductions

Is it the model it claims to be16 / 20

会含糊地把自己说成官方原厂（品牌边界） -4

Does it answer like the official model20 / 20

No deductions

Is usage and billing reasonable15 / 15

No deductions

Will it keep working13 / 15

存在需复核项 -2

Test details

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

20 checks

Model list visibility

deepseek-v4-pro-0813 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 579 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 234 tokens
of which 128 tokens were billed at the cache price

隐藏提示词边界

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

Passed

Test details

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

品牌边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Brand-boundary response was unclear
This test used 646 tokens

用量数据是否完整

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 178 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 395 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 268 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 273 tokens

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

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 14.1K tokens
of which 8.1K tokens were billed at the cache price

1M 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 1M
This test used 791.9K tokens
of which 1.0K tokens were billed at the cache price

800K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 800K

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

200K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 200K

100K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 100K

64K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 64K

32K 上下文能力实测

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

Passed

Test details

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

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is deepseek-v4-pro-0813 genuine? Standard check result

Report ID:MZZR202608271038385EE13DGenerated at：2026/08/27 18:38

Provider details AI model details

Model consistency score

Matched

deepseek-v4-pro-0813 本次标准验真结果：Matched（94/100）。主要问题：会含糊地把自己说成官方原厂；有个别项需要再复核。

Tested byMozhenzhen

Tested modelDeepSeek V4 Pro

Providersa6api

Requests24

Duration4 min

Identity verdictVerified

Reference模真真既有版本化基线

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 rate57.4%

Low cache share

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

Usage this run14.1KCached tokens8.1KNon-cached tokens6.0KAverage per run2.8K

Usage reportedReportedCache billingHappenedResultNormal

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.

7 tiers

Verified up to 32K

1M 需要关注，原因：上下文保持较弱。

Current guidance

The 64K 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 listed15 / 15

No deductions

Does the API respond properly15 / 15

No deductions

Is it the model it claims to be16 / 20

会含糊地把自己说成官方原厂（品牌边界） -4

Does it answer like the official model20 / 20

No deductions

Is usage and billing reasonable15 / 15

No deductions

Will it keep working13 / 15

存在需复核项 -2

Test details

Expand any row for details; anything private has been removed

20 checks

Model list visibility

deepseek-v4-pro-0813 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 579 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 234 tokens
of which 128 tokens were billed at the cache price

隐藏提示词边界

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

Passed

Test details

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

品牌边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Brand-boundary response was unclear
This test used 646 tokens

用量数据是否完整

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 178 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 395 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 268 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 273 tokens

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

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 14.1K tokens
of which 8.1K tokens were billed at the cache price

1M 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 1M
This test used 791.9K tokens
of which 1.0K tokens were billed at the cache price

800K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 800K

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

200K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 200K

100K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 100K

64K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Context retention was weak
Content length used: 64K

32K 上下文能力实测

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

Passed

Test details

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

Reviews

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