Is mimo-v2.5 genuine? Deep check result

Report ID MZZR202607020702418AD658Generated at 2026/07/02 15:02

Matched

mimo-v2.5 本次深度验真结果：Matched（92/100）。主要问题：它不报回用量，没法核对扣费。

92Model consistency score

主要问题：它不报回用量，没法核对扣费。

Tested byMozhenzhen

Tested modelMiMo-V2.5

Providersiksvip

Requests106

Duration2 min

Identity verdictVerified

ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage76.2KThe actual usage reported by the API; this page goes by it.Estimated usage56.0K-163.3KEstimated 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.

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

Low cache share

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

Usage this run31.8KCached tokens25.0KNon-cached tokens6.8KAverage per run6.4K

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.

3 tiers

Verified up to 30K

All tested context tiers (8K / 16K / 30K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 30KTests 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

Matched92/100

主要问题：它不报回用量，没法核对扣费。

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

No deductions

Does the API respond properly9 / 12

它不报回用量，没法核对扣费（用量数据是否完整） -3

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 reasonable5 / 10

它不报回用量，没法核对扣费（用量数据是否完整） -5

Will it keep working25 / 25

No deductions

Test details

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

17 checks

Model list visibility

mimo-v2.5 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

直接询问模型身份，作为低权重红旗信号；自报只能提示明显不一致，不能单独证明官方身份。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 450 tokens
of which 192 tokens were billed at the cache price

指令跟随

要求模型按指定标记回复，判断基础指令跟随和响应可控性。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 284 tokens
of which 192 tokens were billed at the cache price

JSON 结构

要求模型输出固定 JSON，判断结构化响应是否稳定。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 378 tokens
of which 192 tokens were billed at the cache price

品牌边界

要求模型不要伪造官方身份，判断品牌表述是否克制。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 575 tokens
of which 192 tokens were billed at the cache price

MiMo 边界

观察 MiMo 候选模型是否会克制说明模型代码、厂商身份和实测表现不能互相替代。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 600 tokens
of which 192 tokens were billed at the cache price

模型代码锚定

要求模型把本次被检测模型代码、品牌归类和固定标记写入 JSON，便于应用层精确校验。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 400 tokens
of which 192 tokens were billed at the cache price

Model-family test: series and tier identification

按模型代码识别系列或档位，覆盖 Opus/Sonnet/Haiku、GPT/o/Codex、Gemini Pro/Flash、GLM、Kimi、MiniMax 等模型族。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 359 tokens
of which 192 tokens were billed at the cache price

用量数据是否完整

要求短输出并检查响应 usage 是否可被应用层读取，支撑预计消耗与实际消耗对照。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Usage fields were not observable
This test used 519 tokens
of which 192 tokens were billed at the cache price

MiMo

观察 MiMo 候选模型是否能区分模型代码、厂商身份、推理宣称和实测表现。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 1.3K tokens
of which 192 tokens were billed at the cache price

Deep model test: family-specific boundary

针对当前品牌和模型族补充独特边界题，避免只用通用题判断高价值模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 575 tokens
of which 192 tokens were billed at the cache price

复测一致性

同一低温题连续复测两次，观察是否能保持一致响应。 2 次都对。

Passed

Test details

This test ran 2 times: 2 passed.
This test used 655 tokens
of which 448 tokens were billed at the cache price

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

同一长前缀连续请求 5 次，应用层观察 usage、cache usage、token 消耗和费用风险。 5 次都对。

Passed

Test details

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

8K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.9K tokens
of which 5.4K tokens were billed at the cache price

16K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 16K
This test used 11.3K tokens
of which 10.6K tokens were billed at the cache price

30K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 30K
This test used 20.8K tokens
of which 19.8K tokens were billed at the cache price

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is mimo-v2.5 genuine? Deep check result

Report ID:MZZR202607020702418AD658Generated at：2026/07/02 15:02

Provider details AI model details

Model consistency score

Matched

mimo-v2.5 本次深度验真结果：Matched（92/100）。主要问题：它不报回用量，没法核对扣费。

Tested byMozhenzhen

Tested modelMiMo-V2.5

Providersiksvip

Requests106

Duration2 min

Identity verdictVerified

ReferenceMozhenzhen's own test standard

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

Low cache share

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

Usage this run31.8KCached tokens25.0KNon-cached tokens6.8KAverage per run6.4K

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.

3 tiers

Verified up to 30K

All tested context tiers (8K / 16K / 30K) returned reliably.

Results for this test

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

Scoring breakdown

Matched92/100

主要问题：它不报回用量，没法核对扣费。

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

No deductions

Does the API respond properly9 / 12

它不报回用量，没法核对扣费（用量数据是否完整） -3

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 reasonable5 / 10

它不报回用量，没法核对扣费（用量数据是否完整） -5

Will it keep working25 / 25

No deductions

Test details

Expand any row for details; anything private has been removed

17 checks

Model list visibility

mimo-v2.5 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

直接询问模型身份，作为低权重红旗信号；自报只能提示明显不一致，不能单独证明官方身份。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 450 tokens
of which 192 tokens were billed at the cache price

指令跟随

要求模型按指定标记回复，判断基础指令跟随和响应可控性。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 284 tokens
of which 192 tokens were billed at the cache price

JSON 结构

要求模型输出固定 JSON，判断结构化响应是否稳定。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 378 tokens
of which 192 tokens were billed at the cache price

品牌边界

要求模型不要伪造官方身份，判断品牌表述是否克制。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 575 tokens
of which 192 tokens were billed at the cache price

MiMo 边界

观察 MiMo 候选模型是否会克制说明模型代码、厂商身份和实测表现不能互相替代。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 600 tokens
of which 192 tokens were billed at the cache price

模型代码锚定

要求模型把本次被检测模型代码、品牌归类和固定标记写入 JSON，便于应用层精确校验。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 400 tokens
of which 192 tokens were billed at the cache price

Model-family test: series and tier identification

按模型代码识别系列或档位，覆盖 Opus/Sonnet/Haiku、GPT/o/Codex、Gemini Pro/Flash、GLM、Kimi、MiniMax 等模型族。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 359 tokens
of which 192 tokens were billed at the cache price

用量数据是否完整

要求短输出并检查响应 usage 是否可被应用层读取，支撑预计消耗与实际消耗对照。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Usage fields were not observable
This test used 519 tokens
of which 192 tokens were billed at the cache price

MiMo

观察 MiMo 候选模型是否能区分模型代码、厂商身份、推理宣称和实测表现。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 1.3K tokens
of which 192 tokens were billed at the cache price

Deep model test: family-specific boundary

针对当前品牌和模型族补充独特边界题，避免只用通用题判断高价值模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 575 tokens
of which 192 tokens were billed at the cache price

复测一致性

同一低温题连续复测两次，观察是否能保持一致响应。 2 次都对。

Passed

Test details

This test ran 2 times: 2 passed.
This test used 655 tokens
of which 448 tokens were billed at the cache price

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

同一长前缀连续请求 5 次，应用层观察 usage、cache usage、token 消耗和费用风险。 5 次都对。

Passed

Test details

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

8K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.9K tokens
of which 5.4K tokens were billed at the cache price

16K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 16K
This test used 11.3K tokens
of which 10.6K tokens were billed at the cache price

30K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 30K
This test used 20.8K tokens
of which 19.8K tokens were billed at the cache price

Reviews

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