Identity confirmedModel verified
Confirmed as the official hy3
Behavior matches the official hy3.
Brand consistency100/100
Model match score (hy3)100/100
Checks14/17 Passed
- Providers
- TokenHub
- Claimed model
- hy3
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 19
- Duration
- 4 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference108 official models · 5/6 Valid
Answer by answer5 answers: 3 match hy3；another 2 match no model clearly on their own
Similarity to official modelsTop 5
- hy3Claimed model>99%
- gpt-5-mini<1%
- kimi-k2.7-code<1%
- gemini-2.5-flash<1%
- gpt-6-luna<1%
02Test details
17 items · 14 passed · 3 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 hy3 |
| 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 | 5 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the hy family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 hy3 吻合，型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Does not work | The vendor offers a cache price for this model, but none of the repeated requests were billed at it. |
| D-02 | Context length | 128K passed | 32K / 128K: every tier was read in full. |
| 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 |
03Which apps can connect
Tried once per app with hy3, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
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 ratio0.0%
Does not work
The vendor offers a cache price for this model, but none of the repeated requests were billed at it.
Usage this run25.9KCached tokens0Non-cached tokens25.9KAverage per run5.2K
Usage reportedReportedCache billingDid not happenResultDoes not work
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 128K
32K / 128K: every tier was read in full.
Reference windowReference window 256KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 27.0K received
- 128KRead in full · 122.1K received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage222.0KThe actual usage reported by the API; this page goes by it.Estimated usage158.0K-304.3KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches 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
hy3 verification report
Identity confirmedModel verified
Confirmed as the official hy3
Behavior matches the official hy3.
Brand consistency100/100
Model match score (hy3)100/100
Checks14/17 Passed
- Providers
- TokenHub
- Claimed model
- hy3
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 19
- Duration
- 4 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference108 official models · 5/6 Valid
Answer by answer5 answers: 3 match hy3；another 2 match no model clearly on their own
Similarity to official modelsTop 5
- hy3Claimed model>99%
- gpt-5-mini<1%
- kimi-k2.7-code<1%
- gemini-2.5-flash<1%
- gpt-6-luna<1%
02Test details
17 items · 14 passed · 3 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 hy3 |
| 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 | 5 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the hy family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 hy3 吻合，型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Does not work | The vendor offers a cache price for this model, but none of the repeated requests were billed at it. |
| D-02 | Context length | 128K passed | 32K / 128K: every tier was read in full. |
| 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 |
03Which apps can connect
Tried once per app with hy3, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
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 ratio0.0%
Does not work
The vendor offers a cache price for this model, but none of the repeated requests were billed at it.
Usage this run25.9KCached tokens0Non-cached tokens25.9KAverage per run5.2K
Usage reportedReportedCache billingDid not happenResultDoes not work
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 128K
32K / 128K: every tier was read in full.
Reference windowReference window 256KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 27.0K received
- 128KRead in full · 122.1K received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage222.0KThe actual usage reported by the API; this page goes by it.Estimated usage158.0K-304.3KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches 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
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论