Verification report details
Free model verification · Redacted public report

glm-5.1 deep verification model-consistency report

Report ID MZZR202608050732472155ECGenerated at 2026/08/05 15:32

Highly matched

glm-5.1 deep verification result: Highly matched (100/100). All primary checks passed in this run.

100Consistency score

All primary checks passed in this run.

EvaluatorMozhenzhen
Tested modelGLM-5.1
Providers聚光AI
Samples137 probes
Duration3 min 46 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 usage140.5KFrom 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 assessment56% 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 share55.2%
Low cache share

Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.

Observed tokens14.3KCached tokens7.9KNon-cached tokens6.4KAverage per run2.9K
Token usage recordReturnedCache fieldObservedResultNormal
Cache share by testRepresents the API-reported cache share, not the final billing discount.
100%75%50%25%01次:缓存 Token 占比 0.0%,缓存 Token 0,观测 Token 2.8K0.0%1times2次:缓存 Token 占比 91.4%,缓存 Token 2.6K,观测 Token 2.9K91.4%2times3次:缓存 Token 占比 91.9%,缓存 Token 2.6K,观测 Token 2.9K91.9%3times4次:缓存 Token 占比 0.0%,缓存 Token 0,观测 Token 2.8K0.0%4times5次:缓存 Token 占比 92.2%,缓存 Token 2.6K,观测 Token 2.8K92.2%5times
Long-context test

Shows stable responses at different context lengths and the model center reference window.

4 samples
Verified up to 100K

200K Failed,原因:接口鉴权或权限异常。

Reference windowReference window 200KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

200K 档暂不作为当前线路的稳定上下文参考。

Model authenticity score

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

Callability and model visibility10 / 10
No deductions
Protocol and response structure12 / 12
No deductions
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 availability25 / 25
No deductions

Test details

Expand each check to view the redacted evidence notes.

24 checks
Model list visibility

glm-5.1 is visible in the API model list.

Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 109
API path: /v1/models
Visible models: 109
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test evidence
Check: Basic call probe
Status: Passed
Samples: 1
API path: /v1/chat/completions
Quick test: model self-identification

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Quick test: model self-identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 246
Standard test: instruction following

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Standard test: instruction following
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 160
Standard test: JSON structure

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Standard test: JSON structure
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 220
Standard test: tag-structure repetition

General test used as Mozhenzhen verification evidence for the protocol dimension. All samples passed.

Passed
Test evidence
Check: Standard test: tag-structure repetition
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 320
Standard test: hidden-prompt boundary

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Standard test: hidden-prompt boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 218
Standard test: brand boundary

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Standard test: brand boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 409
Standard test: usage observability

General test used as Mozhenzhen verification evidence for the usage dimension. All samples passed.

Passed
Test evidence
Check: Standard test: usage observability
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 171
Deep test: logic-grid reasoning

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Deep test: logic-grid reasoning
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 2.0K
Deep test: retest consistency

General test used as Mozhenzhen verification evidence for the stability dimension. All samples passed.

Passed
Test evidence
Check: Deep test: retest consistency
Status: Passed
Samples: 2
Test type: Text test
Results: Passed 2 / Needs review 0 / Failed 0
Observed tokens: 289
品牌题:GLM 系列证据边界 证据边界

Brand-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: 品牌题:GLM 系列证据边界 证据边界
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 405
深度品牌题:GLM 系列证据边界

Brand-specific test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: 深度品牌题:GLM 系列证据边界
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 1.6K
Model-specific test: model-code anchoring

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Model-specific test: model-code anchoring
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 309
Model-family test: series and tier identification

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Model-family test: series and tier identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 133
Deep model test: family-specific boundary

Model-specific test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Deep model test: family-specific boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 886
Specialty test: token cache usage over 5 rounds

Specialty test used as Mozhenzhen verification evidence. All samples passed.

Passed
Test evidence
Check: Specialty test: token cache usage over 5 rounds
Status: Passed
Samples: 5
Test type: Text test
Specialty: Token cache usage test (may affect real billing)
Results: Passed 5 / Needs review 0 / Failed 0
Observed tokens: 14.3K
Cached tokens: 7.9K
Specialty test: 32K context capability

32K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: Specialty test: 32K context capability
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 32K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 19.4K
专项:64K 上下文能力实测

64K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: 专项:64K 上下文能力实测
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 64K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 38.8K
专项:100K 上下文能力实测

100K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: 专项:100K 上下文能力实测
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 100K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 59.6K
专项:200K 上下文能力实测

200K 长度样本未形成稳定结果,本次按边界样本记录。

Failed
Test evidence
Check: 专项:200K 上下文能力实测
Status: Failed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 200K
Needs review原因:接口鉴权或权限异常
Results: Passed 0 / Needs review 0 / Failed 1
专项:流式 / 非流式一致性

Specialty test used as Mozhenzhen verification evidence. All samples passed.

Passed
Test evidence
Check: 专项:流式 / 非流式一致性
Status: Passed
Samples: 1
Specialty: 流式、工具与结构化输出检测
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 166
专项:工具调用结构

Specialty test used as Mozhenzhen verification evidence. All samples passed.

Passed
Test evidence
Check: 专项:工具调用结构
Status: Passed
Samples: 1
Specialty: 流式、工具与结构化输出检测
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 263
专项:JSON Schema 结构化输出

执行 专项题,用于形成模真真验真证据。 存在样本未完全Passed。

Needs review
Test evidence
Check: 专项:JSON Schema 结构化输出
Status: Needs review
Samples: 1
Specialty: 流式、工具与结构化输出检测
Needs review原因:结构化输出不稳定
Results: Passed 0 / Needs review 1 / Failed 0

Report comments

No public reviews

Be the first to leave a review.

Post an anonymous comment

Rating
5 points
Upload images/video
MozhenzhenAI service research and model verification report
Scan to view reportOpen full report
Free model verification · Supports all text models

glm-5.1 deep verification model-consistency report

Report ID:MZZR202608050732472155ECGenerated at2026/08/05 15:32
Model consistency score

Highly matched

glm-5.1 deep verification result: Highly matched (100/100). All primary checks passed in this run.

EvaluatorMozhenzhen
Tested modelGLM-5.1
Providers聚光AI
Samples137
Duration4 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 usage140.5KFrom 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 assessment56% 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 share55.2%
Low cache share

Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.

Observed tokens14.3KCached tokens7.9KNon-cached tokens6.4KAverage per run2.9K
Token usage recordReturnedCache fieldObservedResultNormal
Cache share by testRepresents the API-reported cache share, not the final billing discount.
100%75%50%25%01次:缓存 Token 占比 0.0%,缓存 Token 0,观测 Token 2.8K0.0%1times2次:缓存 Token 占比 91.4%,缓存 Token 2.6K,观测 Token 2.9K91.4%2times3次:缓存 Token 占比 91.9%,缓存 Token 2.6K,观测 Token 2.9K91.9%3times4次:缓存 Token 占比 0.0%,缓存 Token 0,观测 Token 2.8K0.0%4times5次:缓存 Token 占比 92.2%,缓存 Token 2.6K,观测 Token 2.8K92.2%5times
Long-context test

Shows stable responses at different context lengths and the model center reference window.

4 samples
Verified up to 100K

200K Failed,原因:接口鉴权或权限异常。

Reference windowReference window 200KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

200K 档暂不作为当前线路的稳定上下文参考。

Model authenticity score

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

Callability and model visibility10 / 10
No deductions
Protocol and response structure12 / 12
No deductions
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 availability25 / 25
No deductions

Test details

Expand each check to view the redacted evidence notes.

24 checks
Model list visibility

glm-5.1 is visible in the API model list.

Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 109
API path: /v1/models
Visible models: 109
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test evidence
Check: Basic call probe
Status: Passed
Samples: 1
API path: /v1/chat/completions
Quick test: model self-identification

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Quick test: model self-identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 246
Standard test: instruction following

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Standard test: instruction following
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 160
Standard test: JSON structure

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Standard test: JSON structure
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 220
Standard test: tag-structure repetition

General test used as Mozhenzhen verification evidence for the protocol dimension. All samples passed.

Passed
Test evidence
Check: Standard test: tag-structure repetition
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 320
Standard test: hidden-prompt boundary

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Standard test: hidden-prompt boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 218
Standard test: brand boundary

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Standard test: brand boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 409
Standard test: usage observability

General test used as Mozhenzhen verification evidence for the usage dimension. All samples passed.

Passed
Test evidence
Check: Standard test: usage observability
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 171
Deep test: logic-grid reasoning

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Deep test: logic-grid reasoning
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 2.0K
Deep test: retest consistency

General test used as Mozhenzhen verification evidence for the stability dimension. All samples passed.

Passed
Test evidence
Check: Deep test: retest consistency
Status: Passed
Samples: 2
Test type: Text test
Results: Passed 2 / Needs review 0 / Failed 0
Observed tokens: 289
品牌题:GLM 系列证据边界 证据边界

Brand-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: 品牌题:GLM 系列证据边界 证据边界
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 405
深度品牌题:GLM 系列证据边界

Brand-specific test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: 深度品牌题:GLM 系列证据边界
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 1.6K
Model-specific test: model-code anchoring

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Model-specific test: model-code anchoring
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 309
Model-family test: series and tier identification

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Model-family test: series and tier identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 133
Deep model test: family-specific boundary

Model-specific test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed
Test evidence
Check: Deep model test: family-specific boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 886
Specialty test: token cache usage over 5 rounds

Specialty test used as Mozhenzhen verification evidence. All samples passed.

Passed
Test evidence
Check: Specialty test: token cache usage over 5 rounds
Status: Passed
Samples: 5
Test type: Text test
Specialty: Token cache usage test (may affect real billing)
Results: Passed 5 / Needs review 0 / Failed 0
Observed tokens: 14.3K
Cached tokens: 7.9K
Specialty test: 32K context capability

32K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: Specialty test: 32K context capability
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 32K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 19.4K
专项:64K 上下文能力实测

64K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: 专项:64K 上下文能力实测
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 64K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 38.8K
专项:100K 上下文能力实测

100K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: 专项:100K 上下文能力实测
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 100K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 59.6K
专项:200K 上下文能力实测

200K 长度样本未形成稳定结果,本次按边界样本记录。

Failed
Test evidence
Check: 专项:200K 上下文能力实测
Status: Failed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 200K
Needs review原因:接口鉴权或权限异常
Results: Passed 0 / Needs review 0 / Failed 1
专项:流式 / 非流式一致性

Specialty test used as Mozhenzhen verification evidence. All samples passed.

Passed
Test evidence
Check: 专项:流式 / 非流式一致性
Status: Passed
Samples: 1
Specialty: 流式、工具与结构化输出检测
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 166
专项:工具调用结构

Specialty test used as Mozhenzhen verification evidence. All samples passed.

Passed
Test evidence
Check: 专项:工具调用结构
Status: Passed
Samples: 1
Specialty: 流式、工具与结构化输出检测
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 263
专项:JSON Schema 结构化输出

执行 专项题,用于形成模真真验真证据。 存在样本未完全Passed。

Needs review
Test evidence
Check: 专项:JSON Schema 结构化输出
Status: Needs review
Samples: 1
Specialty: 流式、工具与结构化输出检测
Needs review原因:结构化输出不稳定
Results: Passed 0 / Needs review 1 / Failed 0

Latest user reviews

No public reviews

Be the first to leave a review.

Comments and feedback on this report

Rating
5 points
Upload images/video