glm-5.2 deep verification model-consistency report
Report ID MZZR20260827191134F21BD9Generated at 2026/08/28 03:11
Matched with issues
glm-5.2 deep verification result: Matched with issues (78/100). Main deductions: Model-code anchoring was unstable; Retest consistency was insufficient.
78Consistency score
主要扣分项：模型代码锚定不稳定；复测一致性不足。
EvaluatorMozhenzhen
Tested modelGLM-5.2
ProvidersAPI VibeCoding
Samples27 probes
Duration4 min 42 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 usage43.6KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate90.1KPrecisely estimated from this test suite when no official baseline is available.Variance assessment52% 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.
Tested 5 times
Observed cache share73.5%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens14.3KCached tokens10.5KNon-cached tokens3.8KAverage 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.
1 samples
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.
Model authenticity score
Review API availability, model identity, response completeness, and other checks separately.
Scoring breakdown
Matched with issues78/100
主要扣分项：模型代码锚定不稳定；复测一致性不足。
Callability and model visibility10 / 10
No deductions
Protocol and response structure12 / 12
No deductions
Identity and model match8 / 18
模型代码锚定不稳定（模型级题：模型代码锚定） -10
Core capabilities and model-specific tests22 / 25
模型代码锚定不稳定（模型级题：模型代码锚定） -3
Usage and billing consistency10 / 10
No deductions
Reliability and availability16 / 25
复测一致性不足（深度题：复测一致性） -9
Test details
Expand each check to view the redacted evidence notes.
18 checks
Model list visibility
glm-5.2 is visible in the API model list.
Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 5
API path: /v1/models
Visible models: 5
Basic call probe
The basic API call succeeded and returned a recognizable response.
glm-5.2 deep verification result: Matched with issues (78/100). Main deductions: Model-code anchoring was unstable; Retest consistency was insufficient.
EvaluatorMozhenzhen
Tested modelGLM-5.2
ProvidersAPI VibeCoding
Samples27
Duration5 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 usage43.6KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate90.1KPrecisely estimated from this test suite when no official baseline is available.Variance assessment52% 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.
Tested 5 times
Observed cache share73.5%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens14.3KCached tokens10.5KNon-cached tokens3.8KAverage 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.
1 samples
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.
Model authenticity score
Review API availability, model identity, response completeness, and other checks separately.
Scoring breakdown
Matched with issues78/100
主要扣分项：模型代码锚定不稳定；复测一致性不足。
Callability and model visibility10 / 10
No deductions
Protocol and response structure12 / 12
No deductions
Identity and model match8 / 18
模型代码锚定不稳定（模型级题：模型代码锚定） -10
Core capabilities and model-specific tests22 / 25
模型代码锚定不稳定（模型级题：模型代码锚定） -3
Usage and billing consistency10 / 10
No deductions
Reliability and availability16 / 25
复测一致性不足（深度题：复测一致性） -9
Test details
Expand each check to view the redacted evidence notes.
18 checks
Model list visibility
glm-5.2 is visible in the API model list.
Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 5
API path: /v1/models
Visible models: 5
Basic call probe
The basic API call succeeded and returned a recognizable response.
