Is kimi-k2.7-code genuine? Deep check result

Report ID MZZR2026080407030318DA28Generated at 2026/08/04 15:03

Matched

kimi-k2.7-code 本次深度验真结果：Matched（94/100）。主要问题：有个别项需要再复核；它自称的型号前后对不上。

94Model consistency score

主要问题：有个别项需要再复核；它自称的型号前后对不上。

Tested byMozhenzhen

Tested modelKimi K2.7 Code

Providersconeverse.com

Requests132

Duration4 min 32 sec

Identity verdictVerified

Reference模真真既有版本化基线

Token usage check

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

Reported usage220.0KThe actual usage reported by the API; this page goes by it.Estimated usage312.9KEstimated from this test's requests.Deviation30% 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 rate97.6%

Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run13.7KCached tokens13.3KNon-cached tokens333Average per run2.7K

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

Matched94/100

主要问题：有个别项需要再复核；它自称的型号前后对不上。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly12 / 12

No deductions

Is it the model it claims to be15 / 18

它自称的型号前后对不上（模型身份自报） -3

Does it answer like the official model25 / 25

No deductions

Is usage and billing reasonable10 / 10

No deductions

Will it keep working22 / 25

存在需复核项 -3

Test details

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

24 checks

Model list visibility

kimi-k2.7-code is visible in the API model list.

Passed

Test details

This test ran 104 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

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Self-reported model identity needs review

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 138 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 114 tokens

用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed

Test details

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

逻辑网格推理

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

Passed

Test details

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

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。 2 次都对。

Passed

Test details

This test ran 2 times: 2 passed.
This test used 119 tokens

Kimi 长上下文边界

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 189 tokens

Kimi 长上下文边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 1.1K 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 213 tokens

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 186 tokens

Deep model test: family-specific boundary

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

Passed

Test details

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

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

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 13.7K tokens
of which 13.3K 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 16.5K tokens
of which 16.5K tokens were billed at the cache price

64K 上下文能力实测

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

Passed

Test details

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

100K 上下文能力实测

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

Passed

Test details

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

200K 上下文能力实测

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

Passed

Test details

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

边打字边回和一次性回，结果一样吗

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

Passed

Test details

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

让它调用工具，返回格式对不对

针对这个模型再做一项专门检测。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Protocol structure was unstable

让它按指定格式输出，格式兑现了吗

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

Passed

Test details

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

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is kimi-k2.7-code genuine? Deep check result

Report ID:MZZR2026080407030318DA28Generated at：2026/08/04 15:03

Provider details AI model details

Model consistency score

Matched

kimi-k2.7-code 本次深度验真结果：Matched（94/100）。主要问题：有个别项需要再复核；它自称的型号前后对不上。

Tested byMozhenzhen

Tested modelKimi K2.7 Code

Providersconeverse.com

Requests132

Duration5 min

Identity verdictVerified

Reference模真真既有版本化基线

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 rate97.6%

Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run13.7KCached tokens13.3KNon-cached tokens333Average per run2.7K

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

Matched94/100

主要问题：有个别项需要再复核；它自称的型号前后对不上。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly12 / 12

No deductions

Is it the model it claims to be15 / 18

它自称的型号前后对不上（模型身份自报） -3

Does it answer like the official model25 / 25

No deductions

Is usage and billing reasonable10 / 10

No deductions

Will it keep working22 / 25

存在需复核项 -3

Test details

Expand any row for details; anything private has been removed

24 checks

Model list visibility

kimi-k2.7-code is visible in the API model list.

Passed

Test details

This test ran 104 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

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Self-reported model identity needs review

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 138 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 114 tokens

用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed

Test details

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

逻辑网格推理

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

Passed

Test details

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

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。 2 次都对。

Passed

Test details

This test ran 2 times: 2 passed.
This test used 119 tokens

Kimi 长上下文边界

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 189 tokens

Kimi 长上下文边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 1.1K 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 213 tokens

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 186 tokens

Deep model test: family-specific boundary

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

Passed

Test details

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

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

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 13.7K tokens
of which 13.3K 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 16.5K tokens
of which 16.5K tokens were billed at the cache price

64K 上下文能力实测

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

Passed

Test details

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

100K 上下文能力实测

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

Passed

Test details

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

200K 上下文能力实测

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

Passed

Test details

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

边打字边回和一次性回，结果一样吗

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

Passed

Test details

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

让它调用工具，返回格式对不对

针对这个模型再做一项专门检测。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Protocol structure was unstable

让它按指定格式输出，格式兑现了吗

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

Passed

Test details

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

Reviews

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