Is moonshot-v1-32k genuine? Deep check result
Highly matched
moonshot-v1-32k 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。
All primary checks passed in this run.
moonshot-v1-32k 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。
All primary checks passed in this run.
Reported usage is used; estimates appear only when none is reported.
Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.
The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.
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.
All primary checks passed in this run.
Expand any row for details; anything private has been removed.
moonshot-v1-32k is visible in the API model list.
This test ran 85 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 87 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 26 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 44 tokens
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 86 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 51 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 82 tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 38 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 753 tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 76 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 84 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 397 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 126 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 94 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 119 tokens
针对这个模型再做一项专门检测。 有几次没对上。
This test ran 5 times: 5 passed, 1 need attention. Why it failed: Cache-usage fields were not observable This test used 13.4K tokens
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 19.6K tokens
还没有人评论,来写第一条。
Before you buy AI, check Mozhenzhenmoonshot-v1-32k 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。
Reported usage is used; estimates appear only when none is reported.
Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.
The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.
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.
All primary checks passed in this run.
Expand any row for details; anything private has been removed
moonshot-v1-32k is visible in the API model list.
This test ran 85 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 87 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 26 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 44 tokens
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 86 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 51 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 82 tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 38 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 753 tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 76 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 84 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 397 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 126 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 94 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 119 tokens
针对这个模型再做一项专门检测。 有几次没对上。
This test ran 5 times: 5 passed, 1 need attention. Why it failed: Cache-usage fields were not observable This test used 13.4K tokens
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 19.6K tokens
还没有人评论,来写第一条。
发表评论