Identity confirmedModel verified
Confirmed as the official gpt-6-luna
Behavior matches the official gpt-6-luna.
Brand consistency100/100
Model match score (gpt-6-luna)100/100
Checks14/17 Passed
- Providers
- 灵绘AI
- Claimed model
- gpt-6-luna
- Plan
- Full check
- Reference
- 106 official models
- Requests
- 17
- Duration
- 7 分钟
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采样 FValidReference106 official models · 5/6 Valid
Answer by answer5 answers: 4 match gpt-6-luna；another 1 look more like gpt-5.6-luna
Similarity to official modelsTop 5
- gpt-6-lunaClaimed model>99%
- gpt-5.6-luna<1%
- gpt-5.6-sol<1%
- gpt-6.1-sol<1%
- gpt-6-sol<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 gpt-6-luna |
| 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 OpenAI GPT family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 gpt-6-luna 吻合，型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 98% of repeated requests were billed at the cache price. |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 503. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 503） |
| D-05 | Structured output | Supported | Returned in the required JSON structure |
03Which apps can connect
Tried once per app with gpt-6-luna, 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 ratio98.0%
Cache billing works
On average 98% of repeated requests were billed at the cache price.
Usage this run56.2KCached tokens48.3KNon-cached tokens7.9KAverage per run11.2K
Usage reportedReportedCache billingHappenedResultCache billing 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.
Boundary at 32K
32K failed: 接口返回 HTTP 503.
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接口返回 HTTP 503
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage88.2KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation93% 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-luna verification report
Identity confirmedModel verified
Confirmed as the official gpt-6-luna
Behavior matches the official gpt-6-luna.
Brand consistency100/100
Model match score (gpt-6-luna)100/100
Checks14/17 Passed
- Providers
- 灵绘AI
- Claimed model
- gpt-6-luna
- Plan
- Full check
- Reference
- 106 official models
- Requests
- 17
- Duration
- 7 分钟
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采样 FValidReference106 official models · 5/6 Valid
Answer by answer5 answers: 4 match gpt-6-luna；another 1 look more like gpt-5.6-luna
Similarity to official modelsTop 5
- gpt-6-lunaClaimed model>99%
- gpt-5.6-luna<1%
- gpt-5.6-sol<1%
- gpt-6.1-sol<1%
- gpt-6-sol<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 gpt-6-luna |
| 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 OpenAI GPT family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 gpt-6-luna 吻合，型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 98% of repeated requests were billed at the cache price. |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 503. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 503） |
| D-05 | Structured output | Supported | Returned in the required JSON structure |
03Which apps can connect
Tried once per app with gpt-6-luna, 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 ratio98.0%
Cache billing works
On average 98% of repeated requests were billed at the cache price.
Usage this run56.2KCached tokens48.3KNon-cached tokens7.9KAverage per run11.2K
Usage reportedReportedCache billingHappenedResultCache billing 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.
Boundary at 32K
32K failed: 接口返回 HTTP 503.
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接口返回 HTTP 503
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage88.2KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation93% 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
Anonymous user10/22 11:51
测的是promax分组
发表评论
编辑器加载中…
测的是promax分组
发表评论