Is MiniMax-M2.7 genuine? Deep check result

Report ID MZZR2026070905365589F4B3Generated at 2026/07/09 13:36

Matched

MiniMax-M2.7 本次深度验真结果：Matched（86/100）。主要问题：复杂推理题答得不稳。

86Model consistency score

主要问题：复杂推理题答得不稳。

Tested byMozhenzhen

Tested modelMiniMax-M2.7

ProvidersConeverse AI

Requests110

Duration4 min 20 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 usage236.2KThe actual usage reported by the API; this page goes by it.Estimated usage312.9KEstimated from this test's requests.Deviation25% 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 rate0.0%

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 run14.4KCached tokens0Non-cached tokens14.4KAverage per run2.9K

Usage reportedReportedCache billingDid not happenResultNeeds attention

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 200KModel-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

主要问题：复杂推理题答得不稳。

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 be18 / 18

No deductions

Does it answer like the official model15 / 25

复杂推理题答得不稳（逻辑网格推理） -10

Is usage and billing reasonable10 / 10

No deductions

Will it keep working21 / 25

复杂推理题答得不稳（逻辑网格推理） -4

Test details

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

21 checks

Model list visibility

MiniMax-M2.7 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 276 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

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

用量数据是否完整

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

Passed

Test details

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

逻辑网格推理

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Logic-grid reasoning was unstable

复测一致性

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

Passed

Test details

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

MiniMax 中文能力边界

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

MiniMax 中文能力边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 976 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 388 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 458 tokens

Deep model test: family-specific boundary

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

Passed

Test details

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

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

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

Needs review

Test details

This test ran 5 times: 5 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 14.4K tokens

32K 上下文能力实测

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

Passed

Test details

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

64K 上下文能力实测

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

Passed

Test details

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

100K 上下文能力实测

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

Passed

Test details

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

200K 上下文能力实测

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

Passed

Test details

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

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is MiniMax-M2.7 genuine? Deep check result

Report ID:MZZR2026070905365589F4B3Generated at：2026/07/09 13:36

Provider details AI 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

Matched

MiniMax-M2.7 本次深度验真结果：Matched（86/100）。主要问题：复杂推理题答得不稳。

Tested byMozhenzhen

Tested modelMiniMax-M2.7

ProvidersConeverse AI

Requests110

Duration4 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 rate0.0%

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 run14.4KCached tokens0Non-cached tokens14.4KAverage per run2.9K

Usage reportedReportedCache billingDid not happenResultNeeds attention

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

主要问题：复杂推理题答得不稳。

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 be18 / 18

No deductions

Does it answer like the official model15 / 25

复杂推理题答得不稳（逻辑网格推理） -10

Is usage and billing reasonable10 / 10

No deductions

Will it keep working21 / 25

复杂推理题答得不稳（逻辑网格推理） -4

Test details

Expand any row for details; anything private has been removed

21 checks

Model list visibility

MiniMax-M2.7 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 276 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

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

用量数据是否完整

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

Passed

Test details

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

逻辑网格推理

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Logic-grid reasoning was unstable

复测一致性

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

Passed

Test details

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

MiniMax 中文能力边界

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

MiniMax 中文能力边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 976 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 388 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 458 tokens

Deep model test: family-specific boundary

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

Passed

Test details

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

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

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

Needs review

Test details

This test ran 5 times: 5 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 14.4K tokens

32K 上下文能力实测

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

Passed

Test details

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

64K 上下文能力实测

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

Passed

Test details

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

100K 上下文能力实测

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

Passed

Test details

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

200K 上下文能力实测

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

Passed

Test details

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

Reviews

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