Is glm-5.2 genuine? Deep check result

Report ID MZZR20260827191134F21BD9Generated at 2026/08/28 03:11

Matched with issues

glm-5.2 本次深度验真结果：Matched但Matched with issues（78/100）。主要问题：问它是哪个型号时答案会变；同一个问题反复问，答案会变。

78Model consistency score

主要问题：问它是哪个型号时答案会变；同一个问题反复问，答案会变。

Tested byMozhenzhen

Tested modelGLM-5.2

ProvidersAPI VibeCoding

Requests27

Duration4 min 42 sec

Identity verdictVerified

Reference模真真既有版本化基线

Token usage check

Reported usage is used; estimates appear only when none is reported.

Reported usage43.6KThe actual usage reported by the API; this page goes by it.Estimated usage90.1KEstimated from this test's requests.Deviation52% belowThe reported usage is below the estimate, possibly because of how tokens are counted or compressed.Usage checkBelow the estimateFigures are as reported by the API; your bill is authoritative.

Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request

Share billed at the cache rate73.5%

Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run14.3KCached tokens10.5KNon-cached tokens3.8KAverage per run2.9K

Usage reportedReportedCache billingHappenedResultNormal

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

Long-context test

We test how much it can read at once, then compare that with the officially stated length.

1 tiers

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.

Results for this test

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

Scoring breakdown

Matched with issues78/100

主要问题：问它是哪个型号时答案会变；同一个问题反复问，答案会变。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly12 / 12

No deductions

Is it the model it claims to be8 / 18

问它是哪个型号时答案会变（模型代码锚定） -10

Does it answer like the official model22 / 25

问它是哪个型号时答案会变（模型代码锚定） -3

Is usage and billing reasonable10 / 10

No deductions

Will it keep working16 / 25

同一个问题反复问，答案会变（复测一致性） -9

Test details

Expand any row for details; anything private has been removed.

18 checks

Model list visibility

glm-5.2 is visible in the API model list.

Passed

Test details

This test ran 5 times; result: Passed.

Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed

Test details

This test ran 1 times; result: Passed.

Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 321 tokens

指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 174 tokens

JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 129 tokens

标签结构复述

按官方接口的标准调用，看返回是否规范。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 595 tokens

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 210 tokens

品牌边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 805 tokens

用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 200 tokens

逻辑网格推理

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 280 tokens

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。有几次没对上。

Needs review

Test details

This test ran 2 times: 1 passed, 1 need attention.
Why it failed: Retest consistency was insufficient
This test used 543 tokens

GLM 系列边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 766 tokens

GLM 系列边界

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 2.1K tokens

模型代码锚定

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Model-code anchoring was unstable
This test used 2.1K tokens

Model-family test: series and tier identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 691 tokens

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 916 tokens

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed

Test details

This test ran 5 times: 5 passed.
This test used 14.3K tokens
of which 10.5K tokens were billed at the cache price

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.4K tokens

Reviews

还没有人评论，来写第一条。

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is glm-5.2 genuine? Deep check result

Report ID:MZZR20260827191134F21BD9Generated at：2026/08/28 03:11

Provider details AI model details

Model consistency score

Matched with issues

glm-5.2 本次深度验真结果：Matched但Matched with issues（78/100）。主要问题：问它是哪个型号时答案会变；同一个问题反复问，答案会变。

Tested byMozhenzhen

Tested modelGLM-5.2

ProvidersAPI VibeCoding

Requests27

Duration5 min

Identity verdictVerified

Reference模真真既有版本化基线

Token usage check

Reported usage is used; estimates appear only when none is reported.

Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request

Share billed at the cache rate73.5%

Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run14.3KCached tokens10.5KNon-cached tokens3.8KAverage per run2.9K

Usage reportedReportedCache billingHappenedResultNormal

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

Long-context test

We test how much it can read at once, then compare that with the officially stated length.

1 tiers

Verified up to 32K

All tested context tiers (32K) returned reliably.

Results for this test

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

Scoring breakdown

Matched with issues78/100

主要问题：问它是哪个型号时答案会变；同一个问题反复问，答案会变。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly12 / 12

No deductions

Is it the model it claims to be8 / 18

问它是哪个型号时答案会变（模型代码锚定） -10

Does it answer like the official model22 / 25

问它是哪个型号时答案会变（模型代码锚定） -3

Is usage and billing reasonable10 / 10

No deductions

Will it keep working16 / 25

同一个问题反复问，答案会变（复测一致性） -9

Test details

Expand any row for details; anything private has been removed

18 checks

Model list visibility

glm-5.2 is visible in the API model list.

Passed

Test details

This test ran 5 times; result: Passed.

Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed

Test details

This test ran 1 times; result: Passed.

Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 321 tokens

指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 174 tokens

JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 129 tokens

标签结构复述

按官方接口的标准调用，看返回是否规范。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 595 tokens

隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 210 tokens

品牌边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 805 tokens

用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 200 tokens

逻辑网格推理

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 280 tokens

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。有几次没对上。

Needs review

Test details

This test ran 2 times: 1 passed, 1 need attention.
Why it failed: Retest consistency was insufficient
This test used 543 tokens

GLM 系列边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 766 tokens

GLM 系列边界

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 2.1K tokens

模型代码锚定

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Model-code anchoring was unstable
This test used 2.1K tokens

Model-family test: series and tier identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed

Test details

This test ran 1 times: 1 passed.
This test used 691 tokens

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed

Test details

This test ran 1 times: 1 passed.
This test used 916 tokens

连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed

Test details

This test ran 5 times: 5 passed.
This test used 14.3K tokens
of which 10.5K tokens were billed at the cache price

32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.4K tokens

Reviews

还没有人评论，来写第一条。