Verification report details

Is mimo-v2.5-pro genuine? Quick check result

Report ID MZZR20260708102915E94179Generated at 2026/07/08 18:29

Highly matched

mimo-v2.5-pro 本次快速验真结果：Highly matched（100/100）。本轮主要检测项均已Passed。

100Model consistency score

All primary checks passed in this run.

Tested byMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersConeverse AI
Requests93
Duration1 min 19 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。

Token usage check

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

Reported usage38.1KThe actual usage reported by the API; this page goes by it.Estimated usage76.1KEstimated from this test's requests.Deviation50% 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 rate90.8%
No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run15.9KCached tokens14.4KNon-cached tokens1.5KAverage per run3.2K
Usage reportedReportedCache billingHappenedResultNeeds attention
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次：缓存占比 87.3%，缓存 2.9K token，本次用量 3.3K token87.3%1times第 2 次：缓存占比 85.6%，缓存 2.9K token，本次用量 3.4K token85.6%2times第 3 次：缓存占比 94.0%，缓存 2.9K token，本次用量 3.1K token94.0%3times第 4 次：缓存占比 95.3%，缓存 2.9K token，本次用量 3.0K token95.3%4times第 5 次：缓存占比 92.7%，缓存 2.9K token，本次用量 3.1K token92.7%5times
Long-context test

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

1 tiers
Verified up to 32K

All tested context tiers (32K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests 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

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed30 / 30
No deductions
Does the most basic call work25 / 25
No deductions
Is it the model it claims to be25 / 25
No deductions
Will it keep working20 / 20
No deductions

Test details

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

5 checks
Model list visibility

mimo-v2.5-pro 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 464 tokens
of which 192 tokens were billed at the cache price
连问 5 次，重复内容有没有按缓存价计费

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

Needs review
Test details
This test ran 5 times: 4 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 15.9K tokens
of which 14.4K 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 21.5K tokens
of which 20.7K tokens were billed at the cache price

Reviews

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

发表评论

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

Is mimo-v2.5-pro genuine? Quick check result

Report ID:MZZR20260708102915E94179Generated at：2026/07/08 18:29
Provider detailsAI model details
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
Model consistency score

Highly matched

mimo-v2.5-pro 本次快速验真结果：Highly matched（100/100）。本轮主要检测项均已Passed。

Tested byMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersConeverse AI
Requests93
Duration1 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage38.1KThe actual usage reported by the API; this page goes by it.Estimated usage76.1KEstimated from this test's requests.Deviation50% 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 rate90.8%
No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run15.9KCached tokens14.4KNon-cached tokens1.5KAverage per run3.2K
Usage reportedReportedCache billingHappenedResultNeeds attention
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次：缓存占比 87.3%，缓存 2.9K token，本次用量 3.3K token87.3%1times第 2 次：缓存占比 85.6%，缓存 2.9K token，本次用量 3.4K token85.6%2times第 3 次：缓存占比 94.0%，缓存 2.9K token，本次用量 3.1K token94.0%3times第 4 次：缓存占比 95.3%，缓存 2.9K token，本次用量 3.0K token95.3%4times第 5 次：缓存占比 92.7%，缓存 2.9K token，本次用量 3.1K token92.7%5times
Long-context test

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

1 tiers
Verified up to 32K

All tested context tiers (32K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests 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

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed30 / 30
No deductions
Does the most basic call work25 / 25
No deductions
Is it the model it claims to be25 / 25
No deductions
Will it keep working20 / 20
No deductions

Test details

Expand any row for details; anything private has been removed

5 checks
Model list visibility

mimo-v2.5-pro 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 464 tokens
of which 192 tokens were billed at the cache price
连问 5 次，重复内容有没有按缓存价计费

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

Needs review
Test details
This test ran 5 times: 4 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 15.9K tokens
of which 14.4K 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 21.5K tokens
of which 20.7K tokens were billed at the cache price

Reviews

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

发表评论