Identity confirmedModel verified
Confirmed as the official deepseek-v4-pro
Behavior matches the official deepseek-v4-pro.
Brand consistency100/100
Model match score (deepseek-v4-pro)100/100
Checks12/16 Passed
- Providers
- API 节点 4061053B
- Claimed model
- deepseek-v4-pro
- Plan
- Full check
- Reference
- 109 official models
- Requests
- 11
- Duration
- 3 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference109 official models · 3/3 Valid
Answer by answer3 answers: 2 match deepseek-v4-pro；another 1 match no model clearly on their own
Similarity to official modelsTop 5
- deepseek-v4-proClaimed model>99%
- qwen3-max<1%
- qwen-turbo<1%
- qwen-max<1%
- deepseek-v4.1-flash<1%
02Test details
16 items · 12 passed · 4 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes deepseek-v4-pro |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the DeepSeek family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 deepseek-v4-pro 吻合，型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 401，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 401. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 401） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 401） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 401） |
03Which apps can connect
Tried once per app with deepseek-v4-pro, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Didn't connect | This API rejected the key. Copy a valid key again and check its permission for this model（HTTP 401）Connected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Didn't connect | This API rejected the key. Copy a valid key again and check its permission for this model（HTTP 401）Connected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
接口返回 HTTP 401，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: 接口返回 HTTP 401.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 401
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage38.4KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation97% 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.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Reviews
还没有人评论，来写第一条。
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
deepseek-v4-pro verification report
Identity confirmedModel verified
Confirmed as the official deepseek-v4-pro
Behavior matches the official deepseek-v4-pro.
Brand consistency100/100
Model match score (deepseek-v4-pro)100/100
Checks12/16 Passed
- Providers
- API 节点 4061053B
- Claimed model
- deepseek-v4-pro
- Plan
- Full check
- Reference
- 109 official models
- Requests
- 11
- Duration
- 3 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference109 official models · 3/3 Valid
Answer by answer3 answers: 2 match deepseek-v4-pro；another 1 match no model clearly on their own
Similarity to official modelsTop 5
- deepseek-v4-proClaimed model>99%
- qwen3-max<1%
- qwen-turbo<1%
- qwen-max<1%
- deepseek-v4.1-flash<1%
02Test details
16 items · 12 passed · 4 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes deepseek-v4-pro |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the DeepSeek family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 deepseek-v4-pro 吻合，型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 401，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 401. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 401） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 401） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 401） |
03Which apps can connect
Tried once per app with deepseek-v4-pro, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Didn't connect | This API rejected the key. Copy a valid key again and check its permission for this model（HTTP 401）Connected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Didn't connect | This API rejected the key. Copy a valid key again and check its permission for this model（HTTP 401）Connected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
接口返回 HTTP 401，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: 接口返回 HTTP 401.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 401
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage38.4KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation97% 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.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Reviews
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论