Highly similarBelow confirmation threshold
与官方 gemini-3.8-flash 高度相似
行为特征与官方 gemini-3.8-flash 高度相似，未达确认标准，与 gemini-3.7-flash 难以区分。
Brand consistency100/100
Model match score (gemini-3.8-flash)28/100
Checks11/16 Passed
- Providers
- 星光彼岸 Starlit Horizon
- Claimed model
- gemini-3.8-flash
- Plan
- Full check
- Reference
- 106 official models
- Requests
- 17
- Duration
- 14 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BInvalidIndependent sample C采样 CInvalidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidIndependent sample G采样 GValidIndependent sample H采样 HInvalidIndependent sample I采样 IValidReference106 official models · 5/9 Valid
Answer by answer5 answers: 2 match gemini-3.8-flash；another 2 look more like gemini-3.7-flash；another 1 match no model clearly on their own
Similarity to official modelsTop 5
- gemini-3.7-flash69%
- gemini-3.8-flashClaimed model28%
- gemini-3.6-flash3%
- gemini-3-flash<1%
- gemini-3.5-flash<1%
02Test details
16 items · 11 passed · 5 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes gemini-3.8-flash |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Incomplete | 缺少输入、输出、合计用量 |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 5 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Google Gemini family; brand match score 100 |
| C-03 | Model consistency | Below confirmation threshold | 型号一致度 28，与 gemini-3.7-flash 难以区分 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 502，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 未能提取文档中段的关键信息. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
接口返回 HTTP 502，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: 未能提取文档中段的关键信息.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K未能提取文档中段的关键信息
Token usage check
Reported usage is used; estimates appear only when none is reported.
Estimated usage1.3M-1.8MThe API did not report actual usage; the estimate is shown.DeviationNoneThe API did not report actual usage; only the estimate is shown.Usage checkEstimate onlyFigures are as reported by the API; your bill is authoritative.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Reviews
还没有人评论，来写第一条。
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
gemini-3.8-flash verification report
Highly similarBelow confirmation threshold
与官方 gemini-3.8-flash 高度相似
行为特征与官方 gemini-3.8-flash 高度相似，未达确认标准，与 gemini-3.7-flash 难以区分。
Brand consistency100/100
Model match score (gemini-3.8-flash)28/100
Checks11/16 Passed
- Providers
- 星光彼岸 Starlit Horizon
- Claimed model
- gemini-3.8-flash
- Plan
- Full check
- Reference
- 106 official models
- Requests
- 17
- Duration
- 14 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BInvalidIndependent sample C采样 CInvalidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidIndependent sample G采样 GValidIndependent sample H采样 HInvalidIndependent sample I采样 IValidReference106 official models · 5/9 Valid
Answer by answer5 answers: 2 match gemini-3.8-flash；another 2 look more like gemini-3.7-flash；another 1 match no model clearly on their own
Similarity to official modelsTop 5
- gemini-3.7-flash69%
- gemini-3.8-flashClaimed model28%
- gemini-3.6-flash3%
- gemini-3-flash<1%
- gemini-3.5-flash<1%
02Test details
16 items · 11 passed · 5 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes gemini-3.8-flash |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Incomplete | 缺少输入、输出、合计用量 |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 5 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Google Gemini family; brand match score 100 |
| C-03 | Model consistency | Below confirmation threshold | 型号一致度 28，与 gemini-3.7-flash 难以区分 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 502，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 未能提取文档中段的关键信息. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
接口返回 HTTP 502，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: 未能提取文档中段的关键信息.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K未能提取文档中段的关键信息
Token usage check
Reported usage is used; estimates appear only when none is reported.
Estimated usage1.3M-1.8MThe API did not report actual usage; the estimate is shown.DeviationNoneThe API did not report actual usage; only the estimate is shown.Usage checkEstimate onlyFigures are as reported by the API; your bill is authoritative.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Reviews
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论