Is deepseek-ai/deepseek-v4-pro genuine? Standard check result

Report ID MZZR202609151701199468ECGenerated at 2026/09/16 01:01

Insufficient evidence to determine

Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.

Insufficient evidenceEvidence status

All primary checks passed in this run.

Tested byMozhenzhen

Tested modelDeepSeek V4 Pro

Providers机械臂云端控制台

Requests19

Duration2 min 18 sec

Identity verdictInsufficient evidence to determine

ReferenceNo reference under matching conditions

API and capability checks

The basic API call succeeded and returned a recognizable response.

No issues were recorded in the checks performed. Untested capabilities are outside this conclusion.

API results and model identity are assessed separately. Insufficient evidence does not mean a failed request or a fake model.

Model reference evidence

No reference samples under matching conditions are available for this model.

Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.

Rule version：2026-09-14.v1

Token usage check

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

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

Low cache share

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

Usage this run13.4KCached tokens7.3KNon-cached tokens6.1KAverage 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

Long-context test

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

1 tiers

Verified up to 1M

All tested context tiers (1M) returned reliably.

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths1MTests begin at the longest generated context and step down to verify stable, correct responses.

Test details

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

14 checks

Model list visibility

deepseek-ai/deepseek-v4-pro 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 123 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

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

用量数据是否完整

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

Passed

Test details

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

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

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

Passed

Test details

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

1M 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 1M
This test used 539.1K tokens

Reviews

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

发表评论

编辑器加载中…

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is deepseek-ai/deepseek-v4-pro genuine? Standard check result

Report ID:MZZR202609151701199468ECGenerated at：2026/09/16 01:01

Provider details AI model details

Evidence status

Insufficient evidence to determine

Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.

Tested byMozhenzhen

Tested modelDeepSeek V4 Pro

Providers机械臂云端控制台

Requests19

Duration2 min

Identity verdictInsufficient evidence to determine

ReferenceNo reference under matching conditions

API and capability checks

The basic API call succeeded and returned a recognizable response.

No issues were recorded in the checks performed. Untested capabilities are outside this conclusion.

API results and model identity are assessed separately. Insufficient evidence does not mean a failed request or a fake model.

Model reference evidence

No reference samples under matching conditions are available for this model.

Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.

Rule version：2026-09-14.v1

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 rate54.5%

Low cache share

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

Usage this run13.4KCached tokens7.3KNon-cached tokens6.1KAverage 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

Long-context test

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

1 tiers

Verified up to 1M

All tested context tiers (1M) returned reliably.

Test details

Expand any row for details; anything private has been removed

14 checks

Model list visibility

deepseek-ai/deepseek-v4-pro 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 123 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

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

用量数据是否完整

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

Passed

Test details

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

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

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

Passed

Test details

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

1M 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 1M
This test used 539.1K tokens

Reviews

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

发表评论

编辑器加载中…