Verification report details

Is glm-5.2 genuine? Deep check result

Report ID MZZR202607090714264056BBGenerated at 2026/07/09 15:14

Matched

glm-5.2 本次深度验真结果:Matched(86/100)。主要问题:复杂推理题答得不稳。

86Model consistency score

主要问题:复杂推理题答得不稳。

Tested byMozhenzhen
Tested modelGLM-5.2
ProvidersConeverse AI
Requests113
Duration7 min 12 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。

Token usage check

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

Reported usage1.6MThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation8% 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 rate91.3%
Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run14.4KCached tokens13.1KNon-cached tokens1.2KAverage 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
100%75%50%25%0第 1 次:缓存占比 91.7%,缓存 2.6K token,本次用量 2.9K token91.7%1times第 2 次:缓存占比 91.8%,缓存 2.6K token,本次用量 2.9K token91.8%2times第 3 次:缓存占比 92.1%,缓存 2.6K token,本次用量 2.8K token92.1%3times第 4 次:缓存占比 89.9%,缓存 2.6K token,本次用量 2.9K token89.9%4times第 5 次:缓存占比 91.2%,缓存 2.6K token,本次用量 2.9K token91.2%5times
Long-context test

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

7 tiers
Verified up to 1M

All tested context tiers (32K / 64K / 100K / 200K / 400K / 800K / 1M) returned reliably.

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.

Results for this test

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

Scoring breakdown

Matched86/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 be18 / 18
No deductions
Does it answer like the official model15 / 25
复杂推理题答得不稳(逻辑网格推理) -10
Is usage and billing reasonable10 / 10
No deductions
Will it keep working21 / 25
复杂推理题答得不稳(逻辑网格推理) -4

Test details

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

24 checks
Model list visibility

glm-5.2 is visible in the API model list.

Passed
Test details
This test ran 85 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 296 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 175 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 172 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 350 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 259 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 618 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 201 tokens
逻辑网格推理

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Logic-grid reasoning was unstable
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。

Passed
Test details
This test ran 2 times: 2 passed.
This test used 376 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 581 tokens
GLM 系列边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 2.1K 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 456 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 618 tokens
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.2K tokens
连问 5 次,重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 14.4K tokens
of which 13.1K 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.5K tokens
of which 19.2K tokens were billed at the cache price
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 38.8K tokens
of which 38.5K tokens were billed at the cache price
100K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 100K
This test used 59.4K tokens
of which 59.1K tokens were billed at the cache price
200K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 200K
This test used 118.6K tokens
of which 118.3K tokens were billed at the cache price
400K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 400K
This test used 237.1K tokens
of which 236.7K tokens were billed at the cache price
800K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 800K
This test used 474.0K tokens
of which 473.5K tokens were billed at the cache price
1M 上下文能力实测

1M 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 1M
This test used 611.9K tokens

Reviews

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

发表评论

MozhenzhenBefore 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:MZZR202607090714264056BBGenerated at:2026/07/09 15:14
Provider detailsAI model details
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
Model consistency score

Matched

glm-5.2 本次深度验真结果:Matched(86/100)。主要问题:复杂推理题答得不稳。

Tested byMozhenzhen
Tested modelGLM-5.2
ProvidersConeverse AI
Requests113
Duration7 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage1.6MThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation8% 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 rate91.3%
Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run14.4KCached tokens13.1KNon-cached tokens1.2KAverage 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
100%75%50%25%0第 1 次:缓存占比 91.7%,缓存 2.6K token,本次用量 2.9K token91.7%1times第 2 次:缓存占比 91.8%,缓存 2.6K token,本次用量 2.9K token91.8%2times第 3 次:缓存占比 92.1%,缓存 2.6K token,本次用量 2.8K token92.1%3times第 4 次:缓存占比 89.9%,缓存 2.6K token,本次用量 2.9K token89.9%4times第 5 次:缓存占比 91.2%,缓存 2.6K token,本次用量 2.9K token91.2%5times
Long-context test

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

7 tiers
Verified up to 1M

All tested context tiers (32K / 64K / 100K / 200K / 400K / 800K / 1M) returned reliably.

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.

Results for this test

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

Scoring breakdown

Matched86/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 be18 / 18
No deductions
Does it answer like the official model15 / 25
复杂推理题答得不稳(逻辑网格推理) -10
Is usage and billing reasonable10 / 10
No deductions
Will it keep working21 / 25
复杂推理题答得不稳(逻辑网格推理) -4

Test details

Expand any row for details; anything private has been removed

24 checks
Model list visibility

glm-5.2 is visible in the API model list.

Passed
Test details
This test ran 85 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 296 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 175 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 172 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 350 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 259 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 618 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 201 tokens
逻辑网格推理

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Logic-grid reasoning was unstable
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。

Passed
Test details
This test ran 2 times: 2 passed.
This test used 376 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 581 tokens
GLM 系列边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 2.1K 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 456 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 618 tokens
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.2K tokens
连问 5 次,重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 14.4K tokens
of which 13.1K 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.5K tokens
of which 19.2K tokens were billed at the cache price
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 38.8K tokens
of which 38.5K tokens were billed at the cache price
100K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 100K
This test used 59.4K tokens
of which 59.1K tokens were billed at the cache price
200K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 200K
This test used 118.6K tokens
of which 118.3K tokens were billed at the cache price
400K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 400K
This test used 237.1K tokens
of which 236.7K tokens were billed at the cache price
800K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 800K
This test used 474.0K tokens
of which 473.5K tokens were billed at the cache price
1M 上下文能力实测

1M 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 1M
This test used 611.9K tokens

Reviews

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

发表评论