Is minimax/minimax-m3 genuine? Standard check result
Report ID MZZR2026091517024571680CGenerated at 2026/09/16 01:02
Insufficient evidence to determine
Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.
Insufficient evidenceEvidence status
All primary checks passed in this run.
EvaluatorMozhenzhen
Tested modelMiniMax-M3
ProvidersXiaohui Fan
Times tested19
Duration52 sec
Identity verdictInsufficient evidence to determine
Tested againstBasic capability observations (no calibrated reference)
Model reference evidence
No reference samples under matching conditions are available for this model.
Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.
Service performance score：100 / 100 · Not used to establish model identity
Rule version：2026-09-14.v1
Token usage
We show the usage the endpoint reported itself; estimates appear only when there is no real number.
Observed usage33.5KThis is the real usage the endpoint reported itself, and the main number this page goes by.Usage estimated from the questions79.8KWhen the vendor gives no reference, we estimate from the questions we asked.Variance assessment58% belowIt reported less usage than we estimated; this seller may count or compress differently.Usage conclusionLess than estimatedThis is only the usage the endpoint reported; what you actually pay is on the bill.
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.
Tested 5 times
Share billed at the cache rate57.9%
Low cache share
Caching was used, but only a little; check your bill to see how much it really saves.
Usage this run14.2KCached tokens8.2KNon-cached tokens6.0KAverage per run2.8K
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.
测了 1 档
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.
Test details
Expand any row for details; anything private has been removed.
14 checks
Model list visibility
minimax/minimax-m3 is visible in the API model list.
Passed
Test details
这题测了 2 次，结果：Passed。
Basic call probe
The basic API call succeeded and returned a recognizable response.
Passed
Test details
这题测了 1 次，结果：Passed。
Model self-identification
Asked the model to identify itself; all 1 responses matched the expected name.
Insufficient evidence to determine model identity. API, speed, tool, and token observations are recorded separately and do not establish identity.
EvaluatorMozhenzhen
Tested modelMiniMax-M3
ProvidersXiaohui Fan
Times tested19
Duration52 sec
Identity verdictInsufficient evidence to determine
Tested againstBasic capability observations (no calibrated reference)
Model reference evidence
No reference samples under matching conditions are available for this model.
Model self-identification and individual answers do not establish authenticity. Official references only reflect API behavior at the time of sampling.
Service performance score：100 / 100 · Not used to establish model identity
Rule version：2026-09-14.v1
Token usage
We show the usage the endpoint reported itself; estimates appear only when there is no real number.
Observed usage33.5KThis is the real usage the endpoint reported itself, and the main number this page goes by.Usage estimated from the questions79.8KWhen the vendor gives no reference, we estimate from the questions we asked.Variance assessment58% belowIt reported less usage than we estimated; this seller may count or compress differently.Usage conclusionLess than estimatedThis is only the usage the endpoint reported; what you actually pay is on the bill.
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.
Tested 5 times
Share billed at the cache rate57.9%
Low cache share
Caching was used, but only a little; check your bill to see how much it really saves.
Usage this run14.2KCached tokens8.2KNon-cached tokens6.0KAverage per run2.8K
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.
测了 1 档
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.
Test details
Expand any row for details; anything private has been removed
14 checks
Model list visibility
minimax/minimax-m3 is visible in the API model list.
Passed
Test details
这题测了 2 次，结果：Passed。
Basic call probe
The basic API call succeeded and returned a recognizable response.
Passed
Test details
这题测了 1 次，结果：Passed。
Model self-identification
Asked the model to identify itself; all 1 responses matched the expected name.
