Verification report details

Is kimi-k2.6 genuine? Deep check result

Report ID MZZR202607100520521A5907Generated at 2026/07/10 13:20

Matched with issues

kimi-k2.6 本次深度验真结果:Matched但Matched with issues(84/100)。主要问题:这家的接口当时有故障;有几个关键检测项需要复核。

84Model consistency score

主要问题:这家的接口当时有故障;有几个关键检测项需要复核。

Tested byMozhenzhen
Tested modelKimi K2.6
ProvidersConeverse AI
Requests101
Duration4 min 17 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

Token usage check

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

Reported usage4.1KThe actual usage reported by the API; this page goes by it.Estimated usage6.8KEstimated from this test's requests.Deviation39% 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.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched with issues84/100

主要问题:这家的接口当时有故障;有几个关键检测项需要复核。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly8 / 12
这家的接口当时有故障(用量数据是否完整、逻辑网格推理) -4
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model25 / 25
No deductions
Is usage and billing reasonable10 / 10
No deductions
Will it keep working13 / 25
这家的接口当时有故障(用量数据是否完整、逻辑网格推理) -8有几个关键检测项需要复核 -4

Test details

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

16 checks
Model list visibility

kimi-k2.6 is visible in the API model list.

Passed
Test details
This test ran 85 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 849 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 82 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 170 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 177 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 164 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 348 tokens
用量数据是否完整

核对它报回来的用量和缓存计费。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
逻辑网格推理

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 有几次没对上。

Needs review
Test details
This test ran 2 times: 1 passed, 1 need attention.
Why it failed: API service error
This test used 160 tokens
Kimi 长上下文边界

问它自己是什么模型,看答案对不对。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
Kimi 长上下文边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.1K tokens
模型代码锚定

问它自己是什么模型,看答案对不对。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
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 337 tokens
Deep model test: family-specific boundary

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error

Reviews

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

发表评论

MozhenzhenBefore you buy AI, check Mozhenzhen
Scan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls

Is kimi-k2.6 genuine? Deep check result

Report ID:MZZR202607100520521A5907Generated at:2026/07/10 13:20
Provider detailsAI model details
Model consistency score

Matched with issues

kimi-k2.6 本次深度验真结果:Matched但Matched with issues(84/100)。主要问题:这家的接口当时有故障;有几个关键检测项需要复核。

Tested byMozhenzhen
Tested modelKimi K2.6
ProvidersConeverse AI
Requests101
Duration4 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

Token usage check

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

Reported usage4.1KThe actual usage reported by the API; this page goes by it.Estimated usage6.8KEstimated from this test's requests.Deviation39% 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.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched with issues84/100

主要问题:这家的接口当时有故障;有几个关键检测项需要复核。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly8 / 12
这家的接口当时有故障(用量数据是否完整、逻辑网格推理) -4
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model25 / 25
No deductions
Is usage and billing reasonable10 / 10
No deductions
Will it keep working13 / 25
这家的接口当时有故障(用量数据是否完整、逻辑网格推理) -8有几个关键检测项需要复核 -4

Test details

Expand any row for details; anything private has been removed

16 checks
Model list visibility

kimi-k2.6 is visible in the API model list.

Passed
Test details
This test ran 85 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 849 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 82 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 170 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 177 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 164 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 348 tokens
用量数据是否完整

核对它报回来的用量和缓存计费。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
逻辑网格推理

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 有几次没对上。

Needs review
Test details
This test ran 2 times: 1 passed, 1 need attention.
Why it failed: API service error
This test used 160 tokens
Kimi 长上下文边界

问它自己是什么模型,看答案对不对。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
Kimi 长上下文边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.1K tokens
模型代码锚定

问它自己是什么模型,看答案对不对。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
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 337 tokens
Deep model test: family-specific boundary

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error

Reviews

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

发表评论