Identity confirmed可能型号已列出
Confirmed as the official Gemini 4 Carbon 或 Gemini 4 Argon
这两款都是 Google Gemini 的官方型号，回答特点非常接近，目前分不出这次具体是哪一款。你测的 Gemini 4 Carbon 是其中之一，所以判为身份一致。
Brand consistency100/100
Model match score (这2款合计)100/100
Checks15/17 Passed
- Providers
- wokey.ai
- Claimed model
- gemini-4-carbon
- Plan
- Full check
- Reference
- 111 official models
- Requests
- 16
- Duration
- 8 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference111 official models · 3/3 Valid
Answer by answer3 answers: 3 match gemini-4-carbon / gemini-4-argon
Similarity to official modelsTop 5
可能的型号
- Gemini 4 CarbonClaimed model高度符合Input ¥13.37 / Output ¥66.85 每百万 Token
- Gemini 4 Argon高度符合Input ¥13.37 / Output ¥66.85 每百万 Token
为什么列出2款：这些型号同属 Google Gemini，回答特点几乎一样，单靠这次检测分不出来。
- gemini-3.7-flash<1%
- gemini-3.8-flash<1%
- qwen3.8-max<1%
02Test details
17 items · 15 passed · 2 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-4-carbon |
| 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 | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the Google Gemini family; brand match score 100 |
| C-03 | Model consistency | Match | Confirmed as the official gemini-4-carbon 或 gemini-4-argon |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 44% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K passed | Read in full up to 32K; 128K failed: The endpoint returned no result. |
| 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 | Supported | Returned in the required JSON structure |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio43.6%
Partly works
On average 44% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run24.5KCached tokens8.5KNon-cached tokens16.0KAverage per run4.9K
Usage reportedReportedCache billingHappenedResultPartly works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 32K
Read in full up to 32K; 128K failed: The endpoint returned no result.
Reference windowVerified up to 32KThe model center has no reference context window for this model yet.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 34.3K received
- 128KThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage67.1KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-302.3KEstimated from this test's requests.Deviation57% 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.
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-4-carbon verification report
Identity confirmed可能型号已列出
Confirmed as the official Gemini 4 Carbon 或 Gemini 4 Argon
这两款都是 Google Gemini 的官方型号，回答特点非常接近，目前分不出这次具体是哪一款。你测的 Gemini 4 Carbon 是其中之一，所以判为身份一致。
Brand consistency100/100
Model match score (这2款合计)100/100
Checks15/17 Passed
- Providers
- wokey.ai
- Claimed model
- gemini-4-carbon
- Plan
- Full check
- Reference
- 111 official models
- Requests
- 16
- Duration
- 8 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference111 official models · 3/3 Valid
Answer by answer3 answers: 3 match gemini-4-carbon / gemini-4-argon
Similarity to official modelsTop 5
可能的型号
- Gemini 4 CarbonClaimed model高度符合Input ¥13.37 / Output ¥66.85 每百万 Token
- Gemini 4 Argon高度符合Input ¥13.37 / Output ¥66.85 每百万 Token
为什么列出2款：这些型号同属 Google Gemini，回答特点几乎一样，单靠这次检测分不出来。
- gemini-3.7-flash<1%
- gemini-3.8-flash<1%
- qwen3.8-max<1%
02Test details
17 items · 15 passed · 2 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-4-carbon |
| 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 | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the Google Gemini family; brand match score 100 |
| C-03 | Model consistency | Match | Confirmed as the official gemini-4-carbon 或 gemini-4-argon |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 44% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K passed | Read in full up to 32K; 128K failed: The endpoint returned no result. |
| 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 | Supported | Returned in the required JSON structure |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio43.6%
Partly works
On average 44% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run24.5KCached tokens8.5KNon-cached tokens16.0KAverage per run4.9K
Usage reportedReportedCache billingHappenedResultPartly works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 32K
Read in full up to 32K; 128K failed: The endpoint returned no result.
Reference windowVerified up to 32KThe model center has no reference context window for this model yet.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 34.3K received
- 128KThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage67.1KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-302.3KEstimated from this test's requests.Deviation57% 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.
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
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论