Identity confirmedModel verified
Confirmed as the official grok-4.7
Behavior matches the official grok-4.7.
Brand consistency100/100
Model match score (grok-4.7)100/100
Checks14/17 Passed
- Providers
- API 节点 75145A1D
- Claimed model
- grok-4.7
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 16
- Duration
- 6 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CInvalidReference101 official models · 2/3 Valid
Answer by answer2 answers: 2 match grok-4.7
Similarity to official modelsTop 5
- grok-4.7Claimed model>99%
- gpt-4o-mini<1%
- grok-4.6<1%
- grok-4.5<1%
- doubao-seed-2-1-pro<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 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 | Did not follow instructions | The answer did not return the requested content |
| Identity check | |||
| C-01 | Independent sampling | 2 / 3 valid | Some samples could not be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the xAI Grok family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 grok-4.7 吻合，型号一致度 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 99% of repeated requests were billed at the cache price. |
| D-02 | Context length | 128K passed | 32K / 128K: every tier was read in full. |
| D-03 | Streaming output | Incomplete content | The streamed content did not match the instruction |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Supported | Returned in the required JSON structure |
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 ratio99.5%
Cache billing works
On average 99% of repeated requests were billed at the cache price.
Usage this run73.0KCached tokens59.6KNon-cached tokens13.3KAverage per run14.6K
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.
Verified up to 128K
32K / 128K: every tier was read in full.
Reference windowVerified up to 128KThe model center has no reference context window for this model yet.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 63.1K received
- 128KRead in full · 122.9K received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage287.6KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-272.3KEstimated from this test's requests.Deviation6% aboveThe reported usage is above the estimate; check your bill.Usage checkAbove 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.
Post an anonymous comment
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
grok-4.7 verification report
Identity confirmedModel verified
Confirmed as the official grok-4.7
Behavior matches the official grok-4.7.
Brand consistency100/100
Model match score (grok-4.7)100/100
Checks14/17 Passed
- Providers
- API 节点 75145A1D
- Claimed model
- grok-4.7
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 16
- Duration
- 6 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CInvalidReference101 official models · 2/3 Valid
Answer by answer2 answers: 2 match grok-4.7
Similarity to official modelsTop 5
- grok-4.7Claimed model>99%
- gpt-4o-mini<1%
- grok-4.6<1%
- grok-4.5<1%
- doubao-seed-2-1-pro<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 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 | Did not follow instructions | The answer did not return the requested content |
| Identity check | |||
| C-01 | Independent sampling | 2 / 3 valid | Some samples could not be used for comparison |
| C-02 | Brand consistency | Match | Behavior belongs to the xAI Grok family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 grok-4.7 吻合，型号一致度 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 99% of repeated requests were billed at the cache price. |
| D-02 | Context length | 128K passed | 32K / 128K: every tier was read in full. |
| D-03 | Streaming output | Incomplete content | The streamed content did not match the instruction |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Supported | Returned in the required JSON structure |
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 ratio99.5%
Cache billing works
On average 99% of repeated requests were billed at the cache price.
Usage this run73.0KCached tokens59.6KNon-cached tokens13.3KAverage per run14.6K
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.
Verified up to 128K
32K / 128K: every tier was read in full.
Reference windowVerified up to 128KThe model center has no reference context window for this model yet.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 63.1K received
- 128KRead in full · 122.9K received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage287.6KThe actual usage reported by the API; this page goes by it.Estimated usage157.4K-272.3KEstimated from this test's requests.Deviation6% aboveThe reported usage is above the estimate; check your bill.Usage checkAbove 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.