claude-sonnet-5 deep verification model-consistency report
Report ID MZZR202607210829391A3BD1Generated at 2026/07/21 16:29
Matched with issues
claude-sonnet-5 deep verification result: Matched with issues (76/100). Main deductions: Model-code anchoring was unstable; Model-specific boundary response was unclear; Brand-boundary response was unclear.
76Consistency score
主要扣分项：模型代码锚定不稳定；模型专属边界表达不清；品牌边界表达不清。
EvaluatorMozhenzhen
Tested modelClaude Sonnet 5
ProvidersInfistar
Samples29 probes
Duration5 min 17 sec
Verification versionV10
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 usage2.0MFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate74.9KPrecisely estimated from this test suite when no official baseline is available.Variance assessment2607% 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.
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.
4 samples
Verified up to 950K
200K Failed，原因：接口鉴权或权限异常。
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths950K / 800K / 400K / 200KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance
200K 档暂不作为当前线路的稳定上下文参考。
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.
claude-sonnet-5 deep verification result: Matched with issues (76/100). Main deductions: Model-code anchoring was unstable; Model-specific boundary response was unclear; Brand-boundary response was unclear.
EvaluatorMozhenzhen
Tested modelClaude Sonnet 5
ProvidersInfistar
Samples29
Duration5 min
Test versionV10
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 usage2.0MFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate74.9KPrecisely estimated from this test suite when no official baseline is available.Variance assessment2607% 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.
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.
4 samples
Verified up to 950K
200K Failed，原因：接口鉴权或权限异常。
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths950K / 800K / 400K / 200KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance
200K 档暂不作为当前线路的稳定上下文参考。
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.
