A newer report is availableThis report has been superseded by a later retest. View the latest report。
Identity mismatchSubstitution detected
Does not match the claimed model kimi-k3
行为特征与官方 kimi-k3 明显不符。
Brand consistency0/100
Model match score (kimi-k3)0/100
Checks8/12 Passed
- Relay · group
- a6api · default
- Claimed model
- kimi-k3
- Plan
- Standard verification
- Reference
- 102 official models
- Requests
- 9
- Duration
- 10 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BInvalidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference102 official models · 4/6 Valid
Answer by answer4 answers: 0 match kimi-k3；another 4 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.
- grok-build-0.128%
- claude-opus-4-825%
- claude-haiku-4-513%
- glm-5.3-flash11%
- claude-opus-4-77%
02Test details
12 items · 8 passed · 3 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 |
| 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 | 4 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 0; below the decision threshold |
| C-03 | Model consistency | Mismatch | 型号一致度 0，与官方 kimi-k3 明显不同 |
| 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 |
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage70.8KThe actual usage reported by the API; this page goes by it.Estimated usage3.0K-90.0KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches 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.
Post an anonymous comment
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
kimi-k3 verification report
A newer report is availableThis report has been superseded by a later retest. View the latest report。
Identity mismatchSubstitution detected
Does not match the claimed model kimi-k3
行为特征与官方 kimi-k3 明显不符。
Brand consistency0/100
Model match score (kimi-k3)0/100
Checks8/12 Passed
- Relay · group
- a6api · default
- Claimed model
- kimi-k3
- Plan
- Standard verification
- Reference
- 102 official models
- Requests
- 9
- Duration
- 10 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BInvalidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference102 official models · 4/6 Valid
Answer by answer4 answers: 0 match kimi-k3；another 4 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.
- grok-build-0.128%
- claude-opus-4-825%
- claude-haiku-4-513%
- glm-5.3-flash11%
- claude-opus-4-77%
02Test details
12 items · 8 passed · 3 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 |
| 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 | 4 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 0; below the decision threshold |
| C-03 | Model consistency | Mismatch | 型号一致度 0，与官方 kimi-k3 明显不同 |
| 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 |
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage70.8KThe actual usage reported by the API; this page goes by it.Estimated usage3.0K-90.0KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches 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.