Is deepseek-v4-pro genuine? Deep check result

Report ID MZZR20260808155943DAE31FGenerated at 2026/08/08 23:59

Matched

deepseek-v4-pro 本次深度验真结果：Matched（86/100）。主要问题：这家的接口入口当时打不开；有检测项没Passed。

86Model consistency score

主要问题：这家的接口入口当时打不开；有检测项没Passed。

Tested byMozhenzhen

Tested modelDeepSeek V4 Pro

Providers308422.xyz

Requests23

Duration4 min 47 sec

Identity verdictVerified

Reference模真真既有版本化基线

This call did not complete

Reason for failure

The provider’s API gateway or upstream service did not respond normally.

What to do

Try again later. If this persists, ask the provider to check its API service.

Token usage check

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

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

Low cache share

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

Usage this run16.2KCached tokens12.7KNon-cached tokens3.5KAverage per run3.2K

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.

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

Matched86/100

主要问题：这家的接口入口当时打不开；有检测项没Passed。

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 working15 / 25

这家的接口入口当时打不开（标签结构复述） -8有检测项没Passed -2

Test details

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

22 checks

Model list visibility

deepseek-v4-pro 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 1.0K tokens
of which 384 tokens were billed at the cache price

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

按官方接口的标准调用，看返回是否规范。有几次没对上。

Failed

Test details

This test ran 1 times: 1 failed.

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

品牌边界

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

用量数据是否完整

核对它报回来的用量和缓存计费。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

逻辑网格推理

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

DeepSeek 推理边界

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

DeepSeek 推理边界

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

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

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 16.2K tokens
of which 12.7K 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.8K tokens
of which 256 tokens were billed at the cache price

64K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 35.4K tokens
of which 384 tokens were billed at the cache price

100K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 54.1K tokens
of which 384 tokens were billed at the cache price

200K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 107.5K tokens
of which 384 tokens were billed at the cache price

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
This test used 214.5K tokens
of which 384 tokens were billed at the cache price

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is deepseek-v4-pro genuine? Deep check result

Report ID:MZZR20260808155943DAE31FGenerated at：2026/08/08 23:59

Provider details AI model details

Model consistency score

Matched

deepseek-v4-pro 本次深度验真结果：Matched（86/100）。主要问题：这家的接口入口当时打不开；有检测项没Passed。

Tested byMozhenzhen

Tested modelDeepSeek V4 Pro

Providers308422.xyz

Requests23

Duration5 min

Identity verdictVerified

Reference模真真既有版本化基线

This call did not complete

Reason for failure

The provider’s API gateway or upstream service did not respond normally.

What to do

Try again later. If this persists, ask the provider to check its API service.

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

Low cache share

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

Usage this run16.2KCached tokens12.7KNon-cached tokens3.5KAverage per run3.2K

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.

5 tiers

Verified up to 200K

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

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

Matched86/100

主要问题：这家的接口入口当时打不开；有检测项没Passed。

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 working15 / 25

这家的接口入口当时打不开（标签结构复述） -8有检测项没Passed -2

Test details

Expand any row for details; anything private has been removed

22 checks

Model list visibility

deepseek-v4-pro 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 1.0K tokens
of which 384 tokens were billed at the cache price

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

按官方接口的标准调用，看返回是否规范。有几次没对上。

Failed

Test details

This test ran 1 times: 1 failed.

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

品牌边界

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

用量数据是否完整

核对它报回来的用量和缓存计费。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

逻辑网格推理

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

DeepSeek 推理边界

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

DeepSeek 推理边界

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。前序检测已确认这家的接口入口当时打不开，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

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

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 16.2K tokens
of which 12.7K 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.8K tokens
of which 256 tokens were billed at the cache price

64K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 35.4K tokens
of which 384 tokens were billed at the cache price

100K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 54.1K tokens
of which 384 tokens were billed at the cache price

200K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 107.5K tokens
of which 384 tokens were billed at the cache price

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
This test used 214.5K tokens
of which 384 tokens were billed at the cache price

Reviews

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