Is glm-5.2 genuine? Deep check result

Report ID MZZR202608120248135C9DBEGenerated at 2026/08/12 10:48

Matched

glm-5.2 本次深度验真结果：Matched（86/100）。主要问题：等太久没回应；有检测项没Passed。

86Model consistency score

主要问题：等太久没回应；有检测项没Passed。

Tested byMozhenzhen

Tested modelGLM-5.2

Providersnextapi.store

Requests17

Duration2 min 51 sec

Identity verdictVerified

Reference模真真既有版本化基线

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。

This call did not complete

Reason for failure

The API did not return a result within this test’s waiting period.

What to do

Try again later. If this persists, ask the provider whether this model is responding normally.

Token usage check

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

Reported usage2.8KThe actual usage reported by the API; this page goes by it.Estimated usage12.5KEstimated from this test's requests.Deviation77% 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.

Results for this test

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

Scoring breakdown

Matched86/100

主要问题：等太久没回应；有检测项没Passed。

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

No deductions

Does the API respond properly8 / 12

等太久没回应（逻辑网格推理） -4

Is it the model it claims to be18 / 18

No deductions

Does it answer like the official model25 / 25

No deductions

Is usage and billing reasonable10 / 10

No deductions

Will it keep working15 / 25

等太久没回应（逻辑网格推理） -8有检测项没Passed -2

Test details

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

16 checks

Model list visibility

glm-5.2 is visible in the API model list.

Passed

Test details

This test ran 8 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 283 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 285 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 1.1K tokens

用量数据是否完整

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

Passed

Test details

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

逻辑网格推理

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

Failed

Test details

This test ran 1 times: 1 failed.

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

GLM 系列边界

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

GLM 系列边界

用几道题看它的回答水平像不像官方模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

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:MZZR202608120248135C9DBEGenerated at：2026/08/12 10:48

Provider details AI 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）。主要问题：等太久没回应；有检测项没Passed。

Tested byMozhenzhen

Tested modelGLM-5.2

Providersnextapi.store

Requests17

Duration3 min

Identity verdictVerified

Reference模真真既有版本化基线

This call did not complete

Reason for failure

The API did not return a result within this test’s waiting period.

What to do

Try again later. If this persists, ask the provider whether this model is responding normally.

Token usage check

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

Results for this test

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

Scoring breakdown

Matched86/100

主要问题：等太久没回应；有检测项没Passed。

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

No deductions

Does the API respond properly8 / 12

等太久没回应（逻辑网格推理） -4

Is it the model it claims to be18 / 18

No deductions

Does it answer like the official model25 / 25

No deductions

Is usage and billing reasonable10 / 10

No deductions

Will it keep working15 / 25

等太久没回应（逻辑网格推理） -8有检测项没Passed -2

Test details

Expand any row for details; anything private has been removed

16 checks

Model list visibility

glm-5.2 is visible in the API model list.

Passed

Test details

This test ran 8 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 283 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 285 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 1.1K tokens

用量数据是否完整

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

Passed

Test details

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

逻辑网格推理

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

Failed

Test details

This test ran 1 times: 1 failed.

复测一致性

反复多问几次，看会不会答一半就断或偷偷换模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

GLM 系列边界

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

GLM 系列边界

用几道题看它的回答水平像不像官方模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

模型代码锚定

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Model-family test: series and tier identification

问它自己是什么模型，看答案对不对。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。前序检测已确认等太久没回应，为避免继续制造无效请求，本项已跳过。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: service_failure_circuit_breaker

Reviews

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