Is kimi-k2.6 genuine? Standard check result

Report ID MZZR20260722092600188E96Generated at 2026/07/22 17:26

Matched

kimi-k2.6 本次标准验真结果：Matched（86/100）。主要问题：等太久没回应；有检测项没Passed。

86Model consistency score

主要问题：等太久没回应；有检测项没Passed。

Tested byMozhenzhen

Tested modelKimi K2.6

Providersxinlicloud.top

Requests22

Duration5 min 21 sec

Identity verdictVerified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The API did not return a result within this test’s waiting period.

What to do

Try again later. If this persists, ask the provider whether this model is responding normally.

Token usage check

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

Reported usage243.3KThe actual usage reported by the API; this page goes by it.Estimated usage310.7KEstimated from this test's requests.Deviation22% 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.

Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request

Share billed at the cache rate39.5%

Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run13.9KCached tokens5.5KNon-cached tokens8.4KAverage per run2.8K

Usage reportedReportedCache billingHappenedResultNormal

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

Long-context test

We test how much it can read at once, then compare that with the officially stated length.

4 tiers

Verified up to 200K

All tested context tiers (32K / 64K / 100K / 200K) returned reliably.

Reference windowReference window 256KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200KTests begin at the longest generated context and step down to verify stable, correct responses.

Results for this test

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

Scoring breakdown

Matched86/100

主要问题：等太久没回应；有检测项没Passed。

Can you call it, and is the model listed15 / 15

No deductions

Does the API respond properly11 / 15

等太久没回应（JSON 结构） -4

Is it the model it claims to be20 / 20

No deductions

Does it answer like the official model20 / 20

No deductions

Is usage and billing reasonable15 / 15

No deductions

Will it keep working5 / 15

等太久没回应（JSON 结构） -8有检测项没Passed -2

Test details

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

17 checks

Model list visibility

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

Passed

Test details

This test ran 9 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 119 tokens

指令跟随

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 62 tokens

JSON 结构

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

Failed

Test details

This test ran 1 times: 1 failed.

标签结构复述

按官方接口的标准调用，看返回是否规范。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

品牌边界

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

用量数据是否完整

核对它报回来的用量和缓存计费。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Kimi 长上下文边界

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed

Test details

This test ran 5 times: 5 passed.
This test used 13.9K tokens
of which 5.5K tokens were billed at the cache price

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.3K tokens

64K 上下文能力实测

64K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 38.5K tokens

100K 上下文能力实测

100K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 57.2K tokens

200K 上下文能力实测

200K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 114.0K tokens

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is kimi-k2.6 genuine? Standard check result

Report ID:MZZR20260722092600188E96Generated at：2026/07/22 17:26

Provider details AI model details

Model consistency score

Matched

kimi-k2.6 本次标准验真结果：Matched（86/100）。主要问题：等太久没回应；有检测项没Passed。

Tested byMozhenzhen

Tested modelKimi K2.6

Providersxinlicloud.top

Requests22

Duration5 min

Identity verdictVerified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The API did not return a result within this test’s waiting period.

What to do

Try again later. If this persists, ask the provider whether this model is responding normally.

Token usage check

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

Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request

Share billed at the cache rate39.5%

Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run13.9KCached tokens5.5KNon-cached tokens8.4KAverage per run2.8K

Usage reportedReportedCache billingHappenedResultNormal

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

Long-context test

We test how much it can read at once, then compare that with the officially stated length.

4 tiers

Verified up to 200K

All tested context tiers (32K / 64K / 100K / 200K) returned reliably.

Results for this test

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

Scoring breakdown

Matched86/100

主要问题：等太久没回应；有检测项没Passed。

Can you call it, and is the model listed15 / 15

No deductions

Does the API respond properly11 / 15

等太久没回应（JSON 结构） -4

Is it the model it claims to be20 / 20

No deductions

Does it answer like the official model20 / 20

No deductions

Is usage and billing reasonable15 / 15

No deductions

Will it keep working5 / 15

等太久没回应（JSON 结构） -8有检测项没Passed -2

Test details

Expand any row for details; anything private has been removed

17 checks

Model list visibility

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

Passed

Test details

This test ran 9 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 119 tokens

指令跟随

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 62 tokens

JSON 结构

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

Failed

Test details

This test ran 1 times: 1 failed.

标签结构复述

按官方接口的标准调用，看返回是否规范。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

品牌边界

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

用量数据是否完整

核对它报回来的用量和缓存计费。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Kimi 长上下文边界

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed

Test details

This test ran 5 times: 5 passed.
This test used 13.9K tokens
of which 5.5K tokens were billed at the cache price

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.3K tokens

64K 上下文能力实测

64K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 38.5K tokens

100K 上下文能力实测

100K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 57.2K tokens

200K 上下文能力实测

200K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 114.0K tokens

Reviews

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