Verification report details

Is glm-5.1 genuine? Quick check result

Report ID MZZR202607030911250BF6D6Generated at 2026/07/03 17:11

Highly matched

glm-5.1 本次快速验真结果：Highly matched（100/100）。本轮主要检测项均已Passed。

100Model consistency score

All primary checks passed in this run.

Tested byMozhenzhen
Tested modelGLM-5.1
ProvidersConeverse AI
Requests97
Duration1 min 55 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage165.5KThe actual usage reported by the API; this page goes by it.Estimated usage219.3KEstimated from this test's requests.Deviation25% 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 rate72.7%
Low cache share

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

Usage this run14.4KCached tokens10.5KNon-cached tokens4.0KAverage 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 次：缓存占比 0.0%，缓存 0 token，本次用量 2.9K token0.0%1times第 2 次：缓存占比 92.2%，缓存 2.6K token，本次用量 2.8K token92.2%2times第 3 次：缓存占比 89.8%，缓存 2.6K token，本次用量 2.9K token89.8%3times第 4 次：缓存占比 92.2%，缓存 2.6K token，本次用量 2.8K token92.2%4times第 5 次：缓存占比 89.3%，缓存 2.6K token，本次用量 2.9K token89.3%5times
Long-context test

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

5 tiers
Verified up to 128K

All tested context tiers (8K / 16K / 32K / 64K / 128K) returned reliably.

Reference windowReference window 200KModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 32K / 64K / 128KTests 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

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed30 / 30
No deductions
Does the most basic call work25 / 25
No deductions
Is it the model it claims to be25 / 25
No deductions
Will it keep working20 / 20
No deductions

Test details

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

9 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 251 tokens
连问 5 次，重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 14.4K tokens
of which 10.5K tokens were billed at the cache price
8K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.4K tokens
16K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 16K
This test used 10.1K tokens
32K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.8K tokens
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 39.0K tokens
128K 上下文能力实测

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

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

Reviews

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

发表评论

Latest verification reports/Verification reports
MozhenzhenBefore you buy AI, check Mozhenzhen
Scan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls

Is glm-5.1 genuine? Quick check result

Report ID:MZZR202607030911250BF6D6Generated at：2026/07/03 17:11
Provider detailsAI model details
Model consistency score

Highly matched

glm-5.1 本次快速验真结果：Highly matched（100/100）。本轮主要检测项均已Passed。

Tested byMozhenzhen
Tested modelGLM-5.1
ProvidersConeverse AI
Requests97
Duration2 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage165.5KThe actual usage reported by the API; this page goes by it.Estimated usage219.3KEstimated from this test's requests.Deviation25% 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 rate72.7%
Low cache share

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

Usage this run14.4KCached tokens10.5KNon-cached tokens4.0KAverage 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 次：缓存占比 0.0%，缓存 0 token，本次用量 2.9K token0.0%1times第 2 次：缓存占比 92.2%，缓存 2.6K token，本次用量 2.8K token92.2%2times第 3 次：缓存占比 89.8%，缓存 2.6K token，本次用量 2.9K token89.8%3times第 4 次：缓存占比 92.2%，缓存 2.6K token，本次用量 2.8K token92.2%4times第 5 次：缓存占比 89.3%，缓存 2.6K token，本次用量 2.9K token89.3%5times
Long-context test

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

5 tiers
Verified up to 128K

All tested context tiers (8K / 16K / 32K / 64K / 128K) returned reliably.

Reference windowReference window 200KModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 32K / 64K / 128KTests 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

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed30 / 30
No deductions
Does the most basic call work25 / 25
No deductions
Is it the model it claims to be25 / 25
No deductions
Will it keep working20 / 20
No deductions

Test details

Expand any row for details; anything private has been removed

9 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 251 tokens
连问 5 次，重复内容有没有按缓存价计费

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 14.4K tokens
of which 10.5K tokens were billed at the cache price
8K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.4K tokens
16K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 16K
This test used 10.1K tokens
32K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.8K tokens
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 39.0K tokens
128K 上下文能力实测

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

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

Reviews

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

发表评论