Identity could not be determined this time
行为特征与已收录的官方型号均不够接近,本次无法判定。
- Relay · group
- DasuApi · gork
- Claimed model
- grok-4.7
- Plan
- Full check
- Reference
- 117 official models
- Requests
- 24
- Duration
- 20 分钟
01Identity check
Behaviour compared with each official referenceAnswer by answer2 answers: 0 match grok-4.7;another 2 match no model clearly on their own
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.
- qwen3-next-80b-a3b-thinking51%
- qwen3-235b-a22b29%
- glm-4.5-air7%
- gpt-4o-mini4%
- gpt-5.22%
02Test details
17 items · 9 passed · 8 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 grok-4.7 |
| 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 | 2 / 9 valid | 首轮未能判定,已追加两轮;部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 0; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 0; 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 38% 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 400. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Not called | No tool call was returned; it answered in text |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
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.
On average 38% of repeated requests were billed at the cache price; the rest at the regular price.
Long documents are sent tier by tier to check whether the whole document is read.
Read in full up to 400K; 1M failed: 接口返回 HTTP 400.
- 32KRead in full · 29.0K received
- 128KRead in full · 120.6K received
- 400KRead in full · 376.0K received
- 1M接口返回 HTTP 400
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 Mozhenzhengrok-4.7 verification report
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近,本次无法判定。
- Relay · group
- DasuApi · gork
- Claimed model
- grok-4.7
- Plan
- Full check
- Reference
- 117 official models
- Requests
- 24
- Duration
- 20 分钟
01Identity check
Behaviour compared with each official referenceAnswer by answer2 answers: 0 match grok-4.7;another 2 match no model clearly on their own
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.
- qwen3-next-80b-a3b-thinking51%
- qwen3-235b-a22b29%
- glm-4.5-air7%
- gpt-4o-mini4%
- gpt-5.22%
02Test details
17 items · 9 passed · 8 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 grok-4.7 |
| 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 | 2 / 9 valid | 首轮未能判定,已追加两轮;部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 0; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 0; 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 38% 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 400. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Not called | No tool call was returned; it answered in text |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
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.
On average 38% of repeated requests were billed at the cache price; the rest at the regular price.
Long documents are sent tier by tier to check whether the whole document is read.
Read in full up to 400K; 1M failed: 接口返回 HTTP 400.
- 32KRead in full · 29.0K received
- 128KRead in full · 120.6K received
- 400KRead in full · 376.0K received
- 1M接口返回 HTTP 400
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
还没有人评论,来写第一条。
发表评论