Free model verification · Redacted public report

glm-5.1 deep verification model-consistency report

Report ID MZZR20260709063908D1E6DCGenerated at 2026/07/09 14:39

Matched

glm-5.1 deep verification result: Matched (86/100). Main deductions: Logic-grid reasoning was unstable.

86Consistency score

主要扣分项：逻辑网格推理不稳定。

EvaluatorMozhenzhen

Tested modelGLM-5.1

ProvidersInfistar

Samples110 probes

Duration5 min 2 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 usage260.8KFrom 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 assessment190% 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 share73.1%

Low cache share

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

Observed tokens14.4KCached tokens10.5KNon-cached tokens3.9KAverage per run2.9K

Token usage recordReturnedCache fieldObservedResultNormal

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 200K

All tested context tiers (32K / 64K / 100K / 200K) returned reliably.

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.

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

主要扣分项：逻辑网格推理不稳定。

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 tests15 / 25

逻辑网格推理不稳定（深度题：逻辑网格推理） -10

Usage and billing consistency10 / 10

No deductions

Reliability and availability21 / 25

逻辑网格推理不稳定（深度题：逻辑网格推理） -4

Test details

Expand each check to view the redacted evidence notes.

21 checks

Model list visibility

glm-5.1 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: 418

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: 168

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: 252

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: 286

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: 252

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: 413

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: 202

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
Observed tokens: 2.2K

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: 288

品牌题：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: 446

深度品牌题：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.9K

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: 336

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: 304

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: 854

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.4K
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.8K

专项：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: 39.1K

专项：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.8K

专项：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.9K

Report comments

No public reviews

Be the first to leave a review.

Post an anonymous comment

Rating

5 points

This reportReviews

Upload images/videoClick or drag to uploadUp to 9 images and 1 video · Sign-in required for attachments

AI 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:MZZR20260709063908D1E6DCGenerated at：2026/07/09 14:39

Provider details AI model details

Model consistency score

Matched

glm-5.1 deep verification result: Matched (86/100). Main deductions: Logic-grid reasoning was unstable.

EvaluatorMozhenzhen

Tested modelGLM-5.1

ProvidersInfistar

Samples110

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.

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.1%

Low cache share

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

Observed tokens14.4KCached tokens10.5KNon-cached tokens3.9KAverage per run2.9K

Token usage recordReturnedCache fieldObservedResultNormal

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 200K

All tested context tiers (32K / 64K / 100K / 200K) returned reliably.

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

主要扣分项：逻辑网格推理不稳定。

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 tests15 / 25

逻辑网格推理不稳定（深度题：逻辑网格推理） -10

Usage and billing consistency10 / 10

No deductions

Reliability and availability21 / 25

逻辑网格推理不稳定（深度题：逻辑网格推理） -4

Test details

Expand each check to view the redacted evidence notes.

21 checks

Model list visibility

glm-5.1 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: 418

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: 168

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: 252

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: 286

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: 252

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: 413

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: 202

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
Observed tokens: 2.2K

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: 288

品牌题：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: 446

深度品牌题：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.9K

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: 336

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: 304

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: 854

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.4K
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.8K

专项：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: 39.1K

专项：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.8K

专项：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.9K

Latest user reviews

No public reviews

Be the first to leave a review.

Comments and feedback on this report

Rating

5 points

This reportReviews

Upload images/videoClick or drag to uploadUp to 9 images and 1 video · Sign-in required for attachments