Verification report details

Is minimax/minimax-m3 genuine? Quick check result

Report ID MZZR202607020808536D15FCGenerated at 2026/07/02 16:08

Highly matched

minimax/minimax-m3 本次快速验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

100Model consistency score

All primary checks passed in this run.

Tested byMozhenzhen
Tested modelMiniMax-M3
ProvidersOpenRouter
Requests353
Duration2 min 49 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage1.0MThe actual usage reported by the API; this page goes by it.Estimated usage39.0K-2.2MEstimated 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 rate79.0%
Low cache share

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

Usage this run14.4KCached tokens11.4KNon-cached tokens3.0KAverage per run2.9K
Usage reportedReportedCache billingHappenedResultNormal
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 次:缓存占比 4.0%,缓存 114 token,本次用量 2.9K token4.0%1times第 2 次:缓存占比 97.7%,缓存 2.8K token,本次用量 2.9K token97.7%2times第 3 次:缓存占比 97.9%,缓存 2.8K token,本次用量 2.9K token97.9%3times第 4 次:缓存占比 97.7%,缓存 2.8K token,本次用量 2.9K token97.7%4times第 5 次:缓存占比 98.0%,缓存 2.8K token,本次用量 2.9K token98.0%5times
Long-context test

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

8 tiers
Verified up to 950K

All tested context tiers (8K / 16K / 32K / 64K / 128K / 256K / 512K / 950K) returned reliably.

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 32K / 64K / 128K / 256K / 512K / 950KTests 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.

12 checks
Model list visibility

minimax/minimax-m3 is visible in the API model list.

Passed
Test details
This test ran 338 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 286 tokens
of which 114 tokens were billed at the cache price
连问 5 次,重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 14.4K tokens
of which 11.4K 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 4.6K tokens
of which 114 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 8.7K tokens
of which 114 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 17.0K tokens
of which 128 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.7K tokens
128K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 128K
This test used 66.2K tokens
of which 128 tokens were billed at the cache price
256K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 256K
This test used 132.0K tokens
of which 114 tokens were billed at the cache price
512K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 512K
This test used 263.7K tokens
950K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 950K
This test used 489.3K tokens
of which 114 tokens were billed at the cache price

Reviews

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

发表评论

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

Is minimax/minimax-m3 genuine? Quick check result

Report ID:MZZR202607020808536D15FCGenerated at:2026/07/02 16:08
Provider detailsAI model details
Model consistency score

Highly matched

minimax/minimax-m3 本次快速验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

Tested byMozhenzhen
Tested modelMiniMax-M3
ProvidersOpenRouter
Requests353
Duration3 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage1.0MThe actual usage reported by the API; this page goes by it.Estimated usage39.0K-2.2MEstimated 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 rate79.0%
Low cache share

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

Usage this run14.4KCached tokens11.4KNon-cached tokens3.0KAverage per run2.9K
Usage reportedReportedCache billingHappenedResultNormal
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 次:缓存占比 4.0%,缓存 114 token,本次用量 2.9K token4.0%1times第 2 次:缓存占比 97.7%,缓存 2.8K token,本次用量 2.9K token97.7%2times第 3 次:缓存占比 97.9%,缓存 2.8K token,本次用量 2.9K token97.9%3times第 4 次:缓存占比 97.7%,缓存 2.8K token,本次用量 2.9K token97.7%4times第 5 次:缓存占比 98.0%,缓存 2.8K token,本次用量 2.9K token98.0%5times
Long-context test

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

8 tiers
Verified up to 950K

All tested context tiers (8K / 16K / 32K / 64K / 128K / 256K / 512K / 950K) returned reliably.

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 32K / 64K / 128K / 256K / 512K / 950KTests 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

12 checks
Model list visibility

minimax/minimax-m3 is visible in the API model list.

Passed
Test details
This test ran 338 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 286 tokens
of which 114 tokens were billed at the cache price
连问 5 次,重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 14.4K tokens
of which 11.4K 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 4.6K tokens
of which 114 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 8.7K tokens
of which 114 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 17.0K tokens
of which 128 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.7K tokens
128K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 128K
This test used 66.2K tokens
of which 128 tokens were billed at the cache price
256K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 256K
This test used 132.0K tokens
of which 114 tokens were billed at the cache price
512K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 512K
This test used 263.7K tokens
950K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 950K
This test used 489.3K tokens
of which 114 tokens were billed at the cache price

Reviews

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

发表评论