Matches all of the official gpt-6.1-sol, gpt-6-astra
These two official models answer almost identically, so we cannot tell which one this is. They are close in ability, but their official prices differ about 5× (gpt-6.1-sol input/output per million tokens $2 / $10; gpt-6-astra $10 / $50). If you are paying the gpt-6-astra price, compare what this provider charges for both.
- Providers
- 君黎API
- Claimed model
- gpt-6.1-sol
- Plan
- Standard verification
- Reference
- 103 official models
- Requests
- 5
- Duration
- 58 秒
01Identity check
Behaviour compared with each official referenceAnswer by answer3 answers: 3 match gpt-6.1-sol / gpt-6-astra
- gpt-6.1-sol · gpt-6-astraClaimed model and its near-identical sibling — both match closely>99%
- gpt-6-sol<1%
- gpt-5.6-sol<1%
- gpt-5.6-terra<1%
02Test details
12 items · 11 passed · 1 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 | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the OpenAI GPT family; brand match score 100 |
| C-03 | Model consistency | Exact model undetermined | Matches all of the official gpt-6.1-sol, gpt-6-astra; these models answer almost identically |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
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) |
Token usage check
Reported usage is used; estimates appear only when none is reported.
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 Mozhenzhengpt-6.1-sol verification report
Matches all of the official gpt-6.1-sol, gpt-6-astra
These two official models answer almost identically, so we cannot tell which one this is. They are close in ability, but their official prices differ about 5× (gpt-6.1-sol input/output per million tokens $2 / $10; gpt-6-astra $10 / $50). If you are paying the gpt-6-astra price, compare what this provider charges for both.
- Providers
- 君黎API
- Claimed model
- gpt-6.1-sol
- Plan
- Standard verification
- Reference
- 103 official models
- Requests
- 5
- Duration
- 58 秒
01Identity check
Behaviour compared with each official referenceAnswer by answer3 answers: 3 match gpt-6.1-sol / gpt-6-astra
- gpt-6.1-sol · gpt-6-astraClaimed model and its near-identical sibling — both match closely>99%
- gpt-6-sol<1%
- gpt-5.6-sol<1%
- gpt-5.6-terra<1%
02Test details
12 items · 11 passed · 1 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 | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the OpenAI GPT family; brand match score 100 |
| C-03 | Model consistency | Exact model undetermined | Matches all of the official gpt-6.1-sol, gpt-6-astra; these models answer almost identically |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
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) |
Token usage check
Reported usage is used; estimates appear only when none is reported.
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
还没有人评论,来写第一条。
发表评论