Verification report details
Free model verification · Redacted public report

glm-4.7 quick verification model-consistency report

Report ID MZZR2026070810310645340BGenerated at 2026/07/08 18:31

Highly matched

glm-4.7 quick 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-4.7
ProvidersInfistar
Samples94 probes
Duration1 min 47 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 usage35.0KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate79.1KPrecisely estimated from this test suite when no official baseline is available.Variance assessment56% 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 share70.2%
Low cache share

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

Observed tokens14.6KCached tokens10.2KNon-cached tokens4.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 占比 90.2%，缓存 Token 2.6K，观测 Token 2.8K90.2%2times3次：缓存 Token 占比 82.0%，缓存 Token 2.6K，观测 Token 3.1K82.0%3times4次：缓存 Token 占比 87.6%，缓存 Token 2.6K，观测 Token 2.9K87.6%4times5次：缓存 Token 占比 89.0%，缓存 Token 2.6K，观测 Token 2.9K89.0%5times
Long-context test

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

2 samples
Verified up to 32K

64K 需要关注，原因：接口服务异常。

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

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

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

Highly matched100/100

All primary checks passed in this run.

接口与模型可见30 / 30
No deductions
基础调用与协议25 / 25
No deductions
模型身份红旗25 / 25
No deductions
基础稳定性20 / 20
No deductions

Test details

Expand each check to view the redacted evidence notes.

6 checks
Model list visibility

glm-4.7 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: 255
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.6K
Cached tokens: 10.2K
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 长度样本未形成稳定结果，本次按边界样本记录。

Needs review
Test evidence
Check: 专项：64K 上下文能力实测
Status: Needs review
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 64K
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
Home/Find providers by model/GLM-4.7/Verification reports
MozhenzhenAI service research and model verification report
Scan to view reportOpen full report
Free model verification · Supports all text models

glm-4.7 quick verification model-consistency report

Report ID:MZZR2026070810310645340BGenerated at：2026/07/08 18:31
Provider detailsAI model details
Model consistency score

Highly matched

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

EvaluatorMozhenzhen
Tested modelGLM-4.7
ProvidersInfistar
Samples94
Duration2 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 usage35.0KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate79.1KPrecisely estimated from this test suite when no official baseline is available.Variance assessment56% 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 share70.2%
Low cache share

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

Observed tokens14.6KCached tokens10.2KNon-cached tokens4.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 占比 90.2%，缓存 Token 2.6K，观测 Token 2.8K90.2%2times3次：缓存 Token 占比 82.0%，缓存 Token 2.6K，观测 Token 3.1K82.0%3times4次：缓存 Token 占比 87.6%，缓存 Token 2.6K，观测 Token 2.9K87.6%4times5次：缓存 Token 占比 89.0%，缓存 Token 2.6K，观测 Token 2.9K89.0%5times
Long-context test

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

2 samples
Verified up to 32K

64K 需要关注，原因：接口服务异常。

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

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

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

Highly matched100/100

All primary checks passed in this run.

接口与模型可见30 / 30
No deductions
基础调用与协议25 / 25
No deductions
模型身份红旗25 / 25
No deductions
基础稳定性20 / 20
No deductions

Test details

Expand each check to view the redacted evidence notes.

6 checks
Model list visibility

glm-4.7 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: 255
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.6K
Cached tokens: 10.2K
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 长度样本未形成稳定结果，本次按边界样本记录。

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