A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency72/100
Model match score (gpt-6.1-sol)10/100
Checks11/17 Passed
- Providers
- youyangai.top
- Claimed model
- gpt-6.1-sol
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 24
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidIndependent sample G采样 GValidIndependent sample H采样 HInvalidIndependent sample I采样 IValidReference108 official models · 8/9 Valid
Answer by answer8 answers: 0 match gpt-6.1-sol；another 8 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- gpt-6.1-terra54%
- minimax-m3.1-flash24%
- gpt-6.1-solClaimed model10%
- gpt-6-sol4%
- qwen-max2%
02Test details
17 items · 11 passed · 6 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 gpt-6.1-sol |
| 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 | 8 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 72; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 10; below the decision threshold |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 73% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M failed: 接口返回 HTTP 403. |
| 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 |
03Which apps can connect
Tried once per app with gpt-6.1-sol, 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 ratio72.5%
Partly works
On average 73% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run34.5KCached tokens19.9KNon-cached tokens14.6KAverage per run6.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 400K
Read in full up to 400K; 1M failed: 接口返回 HTTP 403.
Reference windowVerified up to 400KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 34.5K received
- 128KRead in full · 121.0K received
- 400KRead in full · 376.8K received
- 1M接口返回 HTTP 403
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage592.2KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation54% 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
gpt-6.1-sol verification report
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency72/100
Model match score (gpt-6.1-sol)10/100
Checks11/17 Passed
- Providers
- youyangai.top
- Claimed model
- gpt-6.1-sol
- Plan
- Full check
- Reference
- 108 official models
- Requests
- 24
- Duration
- 5 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidIndependent sample G采样 GValidIndependent sample H采样 HInvalidIndependent sample I采样 IValidReference108 official models · 8/9 Valid
Answer by answer8 answers: 0 match gpt-6.1-sol；another 8 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- gpt-6.1-terra54%
- minimax-m3.1-flash24%
- gpt-6.1-solClaimed model10%
- gpt-6-sol4%
- qwen-max2%
02Test details
17 items · 11 passed · 6 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 gpt-6.1-sol |
| 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 | 8 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 72; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 10; below the decision threshold |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 73% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M failed: 接口返回 HTTP 403. |
| 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 |
03Which apps can connect
Tried once per app with gpt-6.1-sol, 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 ratio72.5%
Partly works
On average 73% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run34.5KCached tokens19.9KNon-cached tokens14.6KAverage per run6.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 400K
Read in full up to 400K; 1M failed: 接口返回 HTTP 403.
Reference windowVerified up to 400KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 34.5K received
- 128KRead in full · 121.0K received
- 400KRead in full · 376.8K received
- 1M接口返回 HTTP 403
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage592.2KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation54% 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
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论