MiniMax-M3 deep verification model-consistency report
Report ID MZZR20260709035056CEDFCCGenerated at 2026/07/09 11:50
Doubtful
MiniMax-M3 deep verification result: Doubtful (63/100). Main deductions: Logic-grid reasoning was unstable; Model-code anchoring was unstable; Hidden-prompt boundary was unclear.
63Consistency score
主要扣分项:逻辑网格推理不稳定;模型代码锚定不稳定;隐藏提示词边界不清。
EvaluatorMozhenzhen
Tested modelMiniMax-M3
ProvidersInfistar
Samples113 probes
Duration2 min 29 sec
Verification versionV11
Identity verdictNot verified
Verification basisMozhenzhen versioned baseline
Token usage
Measured API usage is shown first; official baselines or test estimates are used only when measured values are unavailable.
Measured token usage1.4MFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate82.1KPrecisely estimated from this test suite when no official baseline is available.Variance assessment1630% aboveMeasured token usage is above the estimate; review billing or provider logs.Usage conclusionAbove estimateThis reflects usage observability, not the final billed amount.
Token cache usage test
Observes token usage, cache fields, and reuse across rounds; 0% means no cached-token field was observed.
Tested 5 times
Observed cache share78.0%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens14.5KCached tokens11.3KNon-cached tokens3.2KAverage per run2.9K
Cache share by testRepresents the API-reported cache share, not the final billing discount.
Long-context test
Shows stable responses at different context lengths and the model center reference window.
7 samples
Verified up to 1M
All tested context tiers (32K / 64K / 100K / 200K / 400K / 800K / 1M) returned reliably.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200K / 400K / 800K / 1MTests begin at the longest generated context and step down to verify stable, correct responses.
A newer report is availableThis report has been superseded by a later retest. View the latest report。
Model authenticity score
Review API availability, model identity, response completeness, and other checks separately.
MiniMax-M3 deep verification result: Doubtful (63/100). Main deductions: Logic-grid reasoning was unstable; Model-code anchoring was unstable; Hidden-prompt boundary was unclear.
EvaluatorMozhenzhen
Tested modelMiniMax-M3
ProvidersInfistar
Samples113
Duration2 min
Test versionV11
Identity verdictNot verified
Verification basisMozhenzhen versioned baseline
Token usage
Measured API usage is shown first; official baselines or test estimates are used only when measured values are unavailable.
Measured token usage1.4MFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate82.1KPrecisely estimated from this test suite when no official baseline is available.Variance assessment1630% aboveMeasured token usage is above the estimate; review billing or provider logs.Usage conclusionAbove estimateThis reflects usage observability, not the final billed amount.
Token cache usage test
Observes token usage, cache fields, and reuse across rounds; 0% means no cached-token field was observed.
Tested 5 times
Observed cache share78.0%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens14.5KCached tokens11.3KNon-cached tokens3.2KAverage per run2.9K
Cache share by testRepresents the API-reported cache share, not the final billing discount.
Long-context test
Shows stable responses at different context lengths and the model center reference window.
7 samples
Verified up to 1M
All tested context tiers (32K / 64K / 100K / 200K / 400K / 800K / 1M) returned reliably.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200K / 400K / 800K / 1MTests begin at the longest generated context and step down to verify stable, correct responses.
A newer report is availableThis report has been superseded by a later retest. View the latest report。
Model authenticity score
Review API availability, model identity, response completeness, and other checks separately.