Is glm-5.1 genuine? Deep check result

Report ID MZZR20260710054151619321Generated at 2026/07/10 13:41

Matched with issues

glm-5.1 本次深度验真结果：Matched但Matched with issues（84/100）。主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

84Model consistency score

主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

Tested byMozhenzhen

Tested modelGLM-5.1

ProvidersConeverse AI

Requests101

Duration3 min 10 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。

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

Token usage check

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

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

Matched with issues84/100

主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

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

这家的接口当时有故障（品牌边界、用量数据是否完整） -8有几个关键检测项需要复核 -4

Test details

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

16 checks

Model list visibility

glm-5.1 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 291 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

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

品牌边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

用量数据是否完整

核对它报回来的用量和缓存计费。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

逻辑网格推理

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

复测一致性

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

Needs review

Test details

This test ran 2 times: 2 need attention.
Why it failed: API service error

GLM 系列边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

GLM 系列边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

模型代码锚定

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 403 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 347 tokens

Deep model test: family-specific boundary

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

Passed

Test details

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

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is glm-5.1 genuine? Deep check result

Report ID:MZZR20260710054151619321Generated at：2026/07/10 13:41

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 with issues

glm-5.1 本次深度验真结果：Matched但Matched with issues（84/100）。主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

Tested byMozhenzhen

Tested modelGLM-5.1

ProvidersConeverse AI

Requests101

Duration3 min

Identity verdictVerified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

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

Matched with issues84/100

主要问题：这家的接口当时有故障；有几个关键检测项需要复核。

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

这家的接口当时有故障（品牌边界、用量数据是否完整） -8有几个关键检测项需要复核 -4

Test details

Expand any row for details; anything private has been removed

16 checks

Model list visibility

glm-5.1 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 291 tokens

指令跟随

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

Passed

Test details

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

JSON 结构

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

Passed

Test details

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

标签结构复述

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

Passed

Test details

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

隐藏提示词边界

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

Passed

Test details

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

品牌边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

用量数据是否完整

核对它报回来的用量和缓存计费。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

逻辑网格推理

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

复测一致性

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

Needs review

Test details

This test ran 2 times: 2 need attention.
Why it failed: API service error

GLM 系列边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

GLM 系列边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

模型代码锚定

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 403 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 347 tokens

Deep model test: family-specific boundary

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

Passed

Test details

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

Reviews

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