Verification report details

Is gemini-3.1-flash-lite genuine? Standard check result

Report ID MZZR20260708031242494964Generated at 2026/07/08 11:12

Highly matched

gemini-3.1-flash-lite 本次标准验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

100Model consistency score

All primary checks passed in this run.

Tested byMozhenzhen
Tested modelGemini 3.1 Flash Lite
ProvidersConeverse AI
Requests21
Duration40 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage3.4KThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation100% 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 rate0.0%
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.

Usage this run2.7KCached tokens0Non-cached tokens2.7KAverage per run535
Usage reportedReportedCache billingDid not happenResultNeeds attention
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.7K token0.0%1times第 2 次:没有返回用量未返回2times第 3 次:没有返回用量未返回3times第 4 次:没有返回用量未返回4times第 5 次:没有返回用量未返回5times
Long-context test

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

1 tiers
Boundary at 32K

32K 需要关注,原因:接口服务异常。

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

The 32K tier did not return reliably this time; do not rely on this length.

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 listed15 / 15
No deductions
Does the API respond properly15 / 15
No deductions
Is it the model it claims to be20 / 20
No deductions
Does it answer like the official model20 / 20
No deductions
Is usage and billing reasonable15 / 15
No deductions
Will it keep working15 / 15
No deductions

Test details

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

14 checks
Model list visibility

gemini-3.1-flash-lite is visible in the API model list.

Passed
Test details
This test ran 4 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 80 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 21 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 33 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 87 tokens
隐藏提示词边界

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

Passed
Test details
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.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 96 tokens
用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 35 tokens
Gemini 工具和多模态边界

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 88 tokens
模型代码锚定

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

针对这个模型再做一项专门检测。 有几次没对上。

Needs review
Test details
This test ran 5 times: 1 passed, 4 need attention.
Why it failed: API service error
This test used 2.7K tokens
32K 上下文能力实测

32K 长度的内容没能稳定读完,这次就记到这里为止。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 32K

Reviews

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

发表评论

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

Is gemini-3.1-flash-lite genuine? Standard check result

Report ID:MZZR20260708031242494964Generated at:2026/07/08 11:12
Provider detailsAI model details
Model consistency score

Highly matched

gemini-3.1-flash-lite 本次标准验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

Tested byMozhenzhen
Tested modelGemini 3.1 Flash Lite
ProvidersConeverse AI
Requests21
Duration40 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage3.4KThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated from this test's requests.Deviation100% 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 rate0.0%
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.

Usage this run2.7KCached tokens0Non-cached tokens2.7KAverage per run535
Usage reportedReportedCache billingDid not happenResultNeeds attention
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.7K token0.0%1times第 2 次:没有返回用量未返回2times第 3 次:没有返回用量未返回3times第 4 次:没有返回用量未返回4times第 5 次:没有返回用量未返回5times
Long-context test

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

1 tiers
Boundary at 32K

32K 需要关注,原因:接口服务异常。

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

The 32K tier did not return reliably this time; do not rely on this length.

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 listed15 / 15
No deductions
Does the API respond properly15 / 15
No deductions
Is it the model it claims to be20 / 20
No deductions
Does it answer like the official model20 / 20
No deductions
Is usage and billing reasonable15 / 15
No deductions
Will it keep working15 / 15
No deductions

Test details

Expand any row for details; anything private has been removed

14 checks
Model list visibility

gemini-3.1-flash-lite is visible in the API model list.

Passed
Test details
This test ran 4 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 80 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 21 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 33 tokens
标签结构复述

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 87 tokens
隐藏提示词边界

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

Passed
Test details
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.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 96 tokens
用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 35 tokens
Gemini 工具和多模态边界

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 88 tokens
模型代码锚定

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

针对这个模型再做一项专门检测。 有几次没对上。

Needs review
Test details
This test ran 5 times: 1 passed, 4 need attention.
Why it failed: API service error
This test used 2.7K tokens
32K 上下文能力实测

32K 长度的内容没能稳定读完,这次就记到这里为止。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 32K

Reviews

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

发表评论