Highly similarBelow confirmation threshold
与官方 kimi-k3.1-pro 高度相似
行为特征与官方 kimi-k3.1-pro 高度相似，未达确认标准，与 kimi-k3 难以区分。
Brand consistency95/100
Model match score (kimi-k3.1-pro)64/100
Checks9/16 Passed
- Providers
- loveme.space
- Claimed model
- kimi-k3.1-pro
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 17
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CInvalidIndependent sample D采样 DValidIndependent sample E采样 EInvalidIndependent sample F采样 FInvalidIndependent sample G采样 GInvalidIndependent sample H采样 HInvalidIndependent sample I采样 IInvalidReference108 official models · 2/9 Valid
Answer by answer2 answers: 2 match kimi-k3.1-pro
Similarity to official modelsTop 5
- kimi-k3.1-proClaimed model64%
- kimi-k331%
- claude-fable-5-11%
- gpt-5.6-sol1%
- gpt-5.4<1%
02Test details
16 items · 9 passed · 7 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 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 | 2 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Moonshot Kimi family; brand match score 95 |
| C-03 | Model consistency | Below confirmation threshold | 型号一致度 64，与 kimi-k3 难以区分 |
| C-04 | Cross-brand swap check | Needs attention | Similarity to other brands' models totals about 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 404，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 404. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 404） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 404） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 404） |
接口返回 HTTP 404，本项未完成。
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 404.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 404
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage3.8KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-302.3KEstimated from this test's requests.Deviation98% 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
Highly similarBelow confirmation threshold
与官方 kimi-k3.1-pro 高度相似
行为特征与官方 kimi-k3.1-pro 高度相似，未达确认标准，与 kimi-k3 难以区分。
Brand consistency95/100
Model match score (kimi-k3.1-pro)64/100
Checks9/16 Passed
- Providers
- loveme.space
- Claimed model
- kimi-k3.1-pro
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 17
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CInvalidIndependent sample D采样 DValidIndependent sample E采样 EInvalidIndependent sample F采样 FInvalidIndependent sample G采样 GInvalidIndependent sample H采样 HInvalidIndependent sample I采样 IInvalidReference108 official models · 2/9 Valid
Answer by answer2 answers: 2 match kimi-k3.1-pro
Similarity to official modelsTop 5
- kimi-k3.1-proClaimed model64%
- kimi-k331%
- claude-fable-5-11%
- gpt-5.6-sol1%
- gpt-5.4<1%
02Test details
16 items · 9 passed · 7 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 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 | 2 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Moonshot Kimi family; brand match score 95 |
| C-03 | Model consistency | Below confirmation threshold | 型号一致度 64，与 kimi-k3 难以区分 |
| C-04 | Cross-brand swap check | Needs attention | Similarity to other brands' models totals about 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 404，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 404. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 404） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 404） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 404） |
接口返回 HTTP 404，本项未完成。
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 404.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 404
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage3.8KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-302.3KEstimated from this test's requests.Deviation98% 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
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论