Identity mismatchSubstitution detected
Does not match the claimed model kimi-k3.1-pro
行为特征与官方 kimi-k3.1-pro 明显不符。
Brand consistency0/100
Model match score (kimi-k3.1-pro)0/100
Checks11/17 Passed
- Providers
- cnmz.de
- Claimed model
- kimi-k3.1-pro
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 17
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference108 official models · 3/3 Valid
Answer by answer3 answers: 0 match kimi-k3.1-pro；another 3 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- deepseek-v4.1-flash65%
- mimo-v2.515%
- qwen3.7-plus7%
- qwen3.7-max3%
- minimax-m33%
02Test details
17 items · 11 passed · 5 notes · 1 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 kimi-k3.1-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 | Pending review | Brand match score 0; below the decision threshold |
| C-03 | Model consistency | Mismatch | 型号一致度 0，与官方 kimi-k3.1-pro 明显不同 |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 50% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 128K passed | Read in full up to 128K; 400K failed: 接口返回 HTTP 403. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio49.6%
Partly works
On average 50% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run48.5KCached tokens21.7KNon-cached tokens26.8KAverage per run9.7K
Usage reportedReportedCache billingHappenedResultPartly works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 128K
Read in full up to 128K; 400K failed: 接口返回 HTTP 403.
Reference windowVerified up to 128KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400KTested from short to long, stopping at the first failure.
- 32KRead in full · 28.4K received
- 128KRead in full · 119.9K received
- 400K接口返回 HTTP 403
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage202.8KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation84% 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
kimi-k3.1-pro verification report
Identity mismatchSubstitution detected
Does not match the claimed model kimi-k3.1-pro
行为特征与官方 kimi-k3.1-pro 明显不符。
Brand consistency0/100
Model match score (kimi-k3.1-pro)0/100
Checks11/17 Passed
- Providers
- cnmz.de
- Claimed model
- kimi-k3.1-pro
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 17
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference108 official models · 3/3 Valid
Answer by answer3 answers: 0 match kimi-k3.1-pro；another 3 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- deepseek-v4.1-flash65%
- mimo-v2.515%
- qwen3.7-plus7%
- qwen3.7-max3%
- minimax-m33%
02Test details
17 items · 11 passed · 5 notes · 1 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 kimi-k3.1-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 | Pending review | Brand match score 0; below the decision threshold |
| C-03 | Model consistency | Mismatch | 型号一致度 0，与官方 kimi-k3.1-pro 明显不同 |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 50% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 128K passed | Read in full up to 128K; 400K failed: 接口返回 HTTP 403. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio49.6%
Partly works
On average 50% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run48.5KCached tokens21.7KNon-cached tokens26.8KAverage per run9.7K
Usage reportedReportedCache billingHappenedResultPartly works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 128K
Read in full up to 128K; 400K failed: 接口返回 HTTP 403.
Reference windowVerified up to 128KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400KTested from short to long, stopping at the first failure.
- 32KRead in full · 28.4K received
- 128KRead in full · 119.9K received
- 400K接口返回 HTTP 403
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage202.8KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation84% 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
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论