minimax-m3 deep verification model-consistency report
Report ID MZZR20260812024506F4A21DGenerated at 2026/08/12 10:45
Matched with issues
minimax-m3 deep verification result: Matched with issues (77/100). Main deductions: Logic-grid reasoning was unstable; Hidden-prompt boundary was unclear.
77Consistency score
主要扣分项:逻辑网格推理不稳定;隐藏提示词边界不清。
EvaluatorMozhenzhen
Tested modelMiniMax-M3
Providersnextapi.store
Samples24 probes
Duration1 min 15 sec
Verification versionV11
Identity verdictVerified
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 usage5.9KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate6.8KPrecisely estimated from this test suite when no official baseline is available.Variance assessment13% belowMeasured token usage is below the estimate, possibly due to tokenizer, compression, or usage-reporting differences.Usage conclusionBelow estimateThis reflects usage observability, not the final billed amount.
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: Matched with issues (77/100). Main deductions: Logic-grid reasoning was unstable; Hidden-prompt boundary was unclear.
EvaluatorMozhenzhen
Tested modelMiniMax-M3
Providersnextapi.store
Samples24
Duration1 min
Test versionV11
Identity verdictVerified
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 usage5.9KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate6.8KPrecisely estimated from this test suite when no official baseline is available.Variance assessment13% belowMeasured token usage is below the estimate, possibly due to tokenizer, compression, or usage-reporting differences.Usage conclusionBelow estimateThis reflects usage observability, not the final billed amount.
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.