Is glm-5.2 genuine? Deep check result
Matched
glm-5.2 本次深度验真结果:Matched(86/100)。主要问题:等太久没回应;有检测项没Passed。
主要问题:等太久没回应;有检测项没Passed。
glm-5.2 本次深度验真结果:Matched(86/100)。主要问题:等太久没回应;有检测项没Passed。
主要问题:等太久没回应;有检测项没Passed。
The API did not return a result within this test’s waiting period.
Try again later. If this persists, ask the provider whether this model is responding normally.
Reported usage is used; estimates appear only when none is reported.
We test how much it can read at once, then compare that with the officially stated length.
All tested context tiers (32K) returned reliably.
Review API availability, model identity, response completeness, and other checks separately.
主要问题:等太久没回应;有检测项没Passed。
Expand any row for details; anything private has been removed.
glm-5.2 is visible in the API model list.
This test ran 8 times; result: Passed.
The basic API call succeeded and returned a recognizable response.
This test ran 1 times; result: Passed.
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 353 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 156 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 199 tokens
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 355 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 244 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 1.3K tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 188 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 1.8K tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 416 tokens
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 failed.
用几道题看它的回答水平像不像官方模型。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
问它自己是什么模型,看答案对不对。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
问它自己是什么模型,看答案对不对。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
用几道题看它的回答水平像不像官方模型。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 19.5K tokens
还没有人评论,来写第一条。
Before you buy AI, check Mozhenzhenglm-5.2 本次深度验真结果:Matched(86/100)。主要问题:等太久没回应;有检测项没Passed。
The API did not return a result within this test’s waiting period.
Try again later. If this persists, ask the provider whether this model is responding normally.
Reported usage is used; estimates appear only when none is reported.
We test how much it can read at once, then compare that with the officially stated length.
All tested context tiers (32K) returned reliably.
Review API availability, model identity, response completeness, and other checks separately.
主要问题:等太久没回应;有检测项没Passed。
Expand any row for details; anything private has been removed
glm-5.2 is visible in the API model list.
This test ran 8 times; result: Passed.
The basic API call succeeded and returned a recognizable response.
This test ran 1 times; result: Passed.
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 353 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 156 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 199 tokens
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 355 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 244 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 1.3K tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 188 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 1.8K tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 416 tokens
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 failed.
用几道题看它的回答水平像不像官方模型。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
问它自己是什么模型,看答案对不对。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
问它自己是什么模型,看答案对不对。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
用几道题看它的回答水平像不像官方模型。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 19.5K tokens
还没有人评论,来写第一条。
发表评论