claude-opus-4-6 deep verification model-consistency report
Report ID MZZR20260721083548280069Generated at 2026/07/21 16:35
Matched
claude-opus-4-6 deep verification result: Matched (86/100). Main deductions: Upstream response timed out; Failed evidence items were found.
86Consistency score
主要扣分项：上游响应超时；存在Failed证据项。
EvaluatorMozhenzhen
Tested modelClaude Opus 4.6
ProvidersInfistar
Samples23 probes
Duration6 min 4 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 usage53.1KFrom 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 assessment29% 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.
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.
1 samples
边界在 950K
950K Failed，原因：接口鉴权或权限异常。
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths950KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance
950K 档暂不作为当前线路的稳定上下文参考。
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.
Scoring breakdown
Matched86/100
主要扣分项：上游响应超时；存在Failed证据项。
Callability and model visibility10 / 10
No deductions
Protocol and response structure8 / 12
上游响应超时（深度品牌题：Claude 隐藏思考边界） -4
Identity and model match18 / 18
No deductions
Core capabilities and model-specific tests25 / 25
No deductions
Usage and billing consistency10 / 10
No deductions
Reliability and availability15 / 25
上游响应超时（深度品牌题：Claude 隐藏思考边界） -8存在Failed证据项 -2
Test details
Expand each check to view the redacted evidence notes.
15 checks
Model list visibility
claude-opus-4-6 is visible in the API model list.
Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 7
API path: /v1/models
Visible models: 7
Basic call probe
The basic API call succeeded and returned a recognizable response.
claude-opus-4-6 deep verification result: Matched (86/100). Main deductions: Upstream response timed out; Failed evidence items were found.
EvaluatorMozhenzhen
Tested modelClaude Opus 4.6
ProvidersInfistar
Samples23
Duration6 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 usage53.1KFrom 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 assessment29% 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.
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.
1 samples
边界在 950K
950K Failed，原因：接口鉴权或权限异常。
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths950KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance
950K 档暂不作为当前线路的稳定上下文参考。
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.
Scoring breakdown
Matched86/100
主要扣分项：上游响应超时；存在Failed证据项。
Callability and model visibility10 / 10
No deductions
Protocol and response structure8 / 12
上游响应超时（深度品牌题：Claude 隐藏思考边界） -4
Identity and model match18 / 18
No deductions
Core capabilities and model-specific tests25 / 25
No deductions
Usage and billing consistency10 / 10
No deductions
Reliability and availability15 / 25
上游响应超时（深度品牌题：Claude 隐藏思考边界） -8存在Failed证据项 -2
Test details
Expand each check to view the redacted evidence notes.
15 checks
Model list visibility
claude-opus-4-6 is visible in the API model list.
Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 7
API path: /v1/models
Visible models: 7
Basic call probe
The basic API call succeeded and returned a recognizable response.
