Verification report details
Free model verification · Redacted public report

glm-5.2 deep verification model-consistency report

Report ID MZZR202607080804437B658BGenerated at 2026/07/08 16:04

Matched

glm-5.2 本次模型一致性深度验真结果:Matched(88/100)。主要扣分项:接口服务异常。

88Consistency score

主要扣分项:接口服务异常。

EvaluatorMozhenzhen
Tested modelGLM-5.2
ProvidersInfistar
Samples113 probes
Duration6 min 36 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 usage967.0KFrom 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 assessment974% 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 share72.4%
Low cache share

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

Observed tokens14.5KCached tokens10.5KNon-cached tokens4.0KAverage 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 占比 90.0%,缓存 Token 2.6K,观测 Token 2.9K90.0%1times2次:缓存 Token 占比 0.0%,缓存 Token 0,观测 Token 2.9K0.0%2times3次:缓存 Token 占比 89.9%,缓存 Token 2.6K,观测 Token 2.9K89.9%3times4次:缓存 Token 占比 91.3%,缓存 Token 2.6K,观测 Token 2.9K91.3%4times5次:缓存 Token 占比 90.3%,缓存 Token 2.6K,观测 Token 2.9K90.3%5times
Long-context test

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

7 samples
Verified up to 800K

1M 需要关注,原因:接口服务异常。

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

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

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

Matched88/100

主要扣分项:接口服务异常。

Callability and model visibility10 / 10
No deductions
Protocol and response structure8 / 12
接口服务异常(深度题:逻辑网格推理、深度品牌题:GLM 系列证据边界) -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 availability17 / 25
接口服务异常(深度题:逻辑网格推理、深度品牌题:GLM 系列证据边界) -8

Test details

Expand each check to view the redacted evidence notes.

24 checks
Model list visibility

glm-5.2 is visible in the API model list.

Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 85
API path: /v1/models
Visible models: 85
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: 353
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: 148
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: 196
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: 346
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: 220
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: 565
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: 220
Deep test: logic-grid reasoning

执行 通用题,用于形成模真真验真证据,评分维度:ability。 存在样本未完全Passed。

Needs review
Test evidence
Check: Deep test: logic-grid reasoning
Status: Needs review
Samples: 1
Test type: Text test
Needs review原因:接口服务异常
Results: Passed 0 / Needs review 1 / Failed 0
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: 344
品牌题: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: 691
深度品牌题:GLM 系列证据边界

执行 品牌题,用于形成模真真验真证据,评分维度:ability。 存在样本未完全Passed。

Needs review
Test evidence
Check: 深度品牌题:GLM 系列证据边界
Status: Needs review
Samples: 1
Test type: Text test
Needs review原因:接口服务异常
Results: Passed 0 / Needs review 1 / Failed 0
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: 330
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: 311
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: 706
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.5K
Cached tokens: 10.5K
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.6K
专项: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.9K
专项: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 context sample returned reliably and is included as evidence for this run.

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

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

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

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

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

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

Needs review
Test evidence
Check: 专项:1M 上下文能力实测
Status: Needs review
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 1M
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.2 deep verification model-consistency report

Report ID:MZZR202607080804437B658BGenerated at2026/07/08 16:04
Model consistency score

Matched

glm-5.2 本次模型一致性深度验真结果:Matched(88/100)。主要扣分项:接口服务异常。

EvaluatorMozhenzhen
Tested modelGLM-5.2
ProvidersInfistar
Samples113
Duration7 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 usage967.0KFrom 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 assessment974% 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 share72.4%
Low cache share

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

Observed tokens14.5KCached tokens10.5KNon-cached tokens4.0KAverage 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 占比 90.0%,缓存 Token 2.6K,观测 Token 2.9K90.0%1times2次:缓存 Token 占比 0.0%,缓存 Token 0,观测 Token 2.9K0.0%2times3次:缓存 Token 占比 89.9%,缓存 Token 2.6K,观测 Token 2.9K89.9%3times4次:缓存 Token 占比 91.3%,缓存 Token 2.6K,观测 Token 2.9K91.3%4times5次:缓存 Token 占比 90.3%,缓存 Token 2.6K,观测 Token 2.9K90.3%5times
Long-context test

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

7 samples
Verified up to 800K

1M 需要关注,原因:接口服务异常。

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

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

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

Matched88/100

主要扣分项:接口服务异常。

Callability and model visibility10 / 10
No deductions
Protocol and response structure8 / 12
接口服务异常(深度题:逻辑网格推理、深度品牌题:GLM 系列证据边界) -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 availability17 / 25
接口服务异常(深度题:逻辑网格推理、深度品牌题:GLM 系列证据边界) -8

Test details

Expand each check to view the redacted evidence notes.

24 checks
Model list visibility

glm-5.2 is visible in the API model list.

Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 85
API path: /v1/models
Visible models: 85
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: 353
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: 148
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: 196
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: 346
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: 220
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: 565
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: 220
Deep test: logic-grid reasoning

执行 通用题,用于形成模真真验真证据,评分维度:ability。 存在样本未完全Passed。

Needs review
Test evidence
Check: Deep test: logic-grid reasoning
Status: Needs review
Samples: 1
Test type: Text test
Needs review原因:接口服务异常
Results: Passed 0 / Needs review 1 / Failed 0
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: 344
品牌题: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: 691
深度品牌题:GLM 系列证据边界

执行 品牌题,用于形成模真真验真证据,评分维度:ability。 存在样本未完全Passed。

Needs review
Test evidence
Check: 深度品牌题:GLM 系列证据边界
Status: Needs review
Samples: 1
Test type: Text test
Needs review原因:接口服务异常
Results: Passed 0 / Needs review 1 / Failed 0
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: 330
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: 311
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: 706
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.5K
Cached tokens: 10.5K
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.6K
专项: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.9K
专项: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 context sample returned reliably and is included as evidence for this run.

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

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

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

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

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

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

Needs review
Test evidence
Check: 专项:1M 上下文能力实测
Status: Needs review
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 1M
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