Is gemini-3.1-flash-lite genuine? Deep check result
Highly matched
gemini-3.1-flash-lite 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。
All primary checks passed in this run.
gemini-3.1-flash-lite 本次深度验真结果: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.
800K 需要关注,原因:接口服务异常。
The 800K tier did not return reliably this time; do not rely on this length.
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.
gemini-3.1-flash-lite is visible in the API model list.
This test ran 4 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 88 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 21 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 33 tokens
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 87 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 48 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 79 tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 35 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 821 tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 66 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 90 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 449 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 124 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 96 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 152 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.9K tokens
64K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 64K This test used 39.7K tokens
100K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 100K This test used 62.6K tokens
200K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 200K This test used 125.2K tokens
400K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 400K This test used 250.4K tokens
800K 长度的内容没能稳定读完,这次就记到这里为止。
This test ran 1 times: 1 need attention. Why it failed: API service error Content length used: 800K
还没有人评论,来写第一条。
Before you buy AI, check Mozhenzhengemini-3.1-flash-lite 本次深度验真结果: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.
800K 需要关注,原因:接口服务异常。
The 800K tier did not return reliably this time; do not rely on this length.
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
gemini-3.1-flash-lite is visible in the API model list.
This test ran 4 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 88 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 21 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 33 tokens
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 87 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 48 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 79 tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 35 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 821 tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 66 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 90 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 449 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 124 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 96 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 152 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.9K tokens
64K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 64K This test used 39.7K tokens
100K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 100K This test used 62.6K tokens
200K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 200K This test used 125.2K tokens
400K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 400K This test used 250.4K tokens
800K 长度的内容没能稳定读完,这次就记到这里为止。
This test ran 1 times: 1 need attention. Why it failed: API service error Content length used: 800K
还没有人评论,来写第一条。
发表评论