Verification report details

Is grok-4.5 genuine? Quick check result

Report ID MZZR2026081304211458C597Generated at 2026/08/13 12:21

Highly matched

grok-4.5 本次快速验真结果：Highly matched（100/100）。本轮主要检测项均已Passed。

100Model consistency score

All primary checks passed in this run.

Tested byMozhenzhen
Tested modelGrok 4.5
Providersapikey
Requests10
Duration1 min 24 sec
Identity verdictVerified
Reference禾维

Token usage check

Reported usage is used; estimates appear only when none is reported.

Reported usage37.8KThe actual usage reported by the API; this page goes by it.Estimated usage73.3KEstimated from this test's requests.Deviation48% 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.
Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request
Share billed at the cache rate54.1%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run16.1KCached tokens8.7KNon-cached tokens7.4KAverage per run3.2K
Usage reportedReportedCache billingHappenedResultNormal
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次：缓存占比 4.0%，缓存 128 token，本次用量 3.2K token4.0%1times第 2 次：缓存占比 88.5%，缓存 2.8K token，本次用量 3.2K token88.5%2times第 3 次：缓存占比 87.0%，缓存 2.8K token，本次用量 3.2K token87.0%3times第 4 次：缓存占比 4.0%，缓存 128 token，本次用量 3.2K token4.0%4times第 5 次：缓存占比 86.6%，缓存 2.8K token，本次用量 3.3K token86.6%5times
Long-context test

We test how much it can read at once, then compare that with the officially stated length.

1 tiers
Verified up to 32K

All tested context tiers (32K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests begin at the longest generated context and step down to verify stable, correct responses.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed30 / 30
No deductions
Does the most basic call work25 / 25
No deductions
Is it the model it claims to be25 / 25
No deductions
Will it keep working20 / 20
No deductions

Test details

Expand any row for details; anything private has been removed.

5 checks
Model list visibility

grok-4.5 is visible in the API model list.

Passed
Test details
This test ran 2 times; result: Passed.
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test details
This test ran 1 times; result: Passed.
Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.6K tokens
of which 192 tokens were billed at the cache price
连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed
Test details
This test ran 5 times: 5 passed.
This test used 16.1K tokens
of which 8.7K tokens were billed at the cache price
32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.5K tokens
of which 192 tokens were billed at the cache price

Reviews

还没有人评论，来写第一条。

发表评论

Home/Model verification/Verification reports
MozhenzhenBefore you buy AI, check Mozhenzhen
Scan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls

Is grok-4.5 genuine? Quick check result

Report ID:MZZR2026081304211458C597Generated at：2026/08/13 12:21
Provider detailsAI model details
Model consistency score

Highly matched

grok-4.5 本次快速验真结果：Highly matched（100/100）。本轮主要检测项均已Passed。

Tested byMozhenzhen
Tested modelGrok 4.5
Providersapikey
Requests10
Duration1 min
Identity verdictVerified
Reference禾维

Token usage check

Reported usage is used; estimates appear only when none is reported.

Reported usage37.8KThe actual usage reported by the API; this page goes by it.Estimated usage73.3KEstimated from this test's requests.Deviation48% 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.
Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request
Share billed at the cache rate54.1%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run16.1KCached tokens8.7KNon-cached tokens7.4KAverage per run3.2K
Usage reportedReportedCache billingHappenedResultNormal
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次：缓存占比 4.0%，缓存 128 token，本次用量 3.2K token4.0%1times第 2 次：缓存占比 88.5%，缓存 2.8K token，本次用量 3.2K token88.5%2times第 3 次：缓存占比 87.0%，缓存 2.8K token，本次用量 3.2K token87.0%3times第 4 次：缓存占比 4.0%，缓存 128 token，本次用量 3.2K token4.0%4times第 5 次：缓存占比 86.6%，缓存 2.8K token，本次用量 3.3K token86.6%5times
Long-context test

We test how much it can read at once, then compare that with the officially stated length.

1 tiers
Verified up to 32K

All tested context tiers (32K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests begin at the longest generated context and step down to verify stable, correct responses.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

Can you call it, and is the model listed30 / 30
No deductions
Does the most basic call work25 / 25
No deductions
Is it the model it claims to be25 / 25
No deductions
Will it keep working20 / 20
No deductions

Test details

Expand any row for details; anything private has been removed

5 checks
Model list visibility

grok-4.5 is visible in the API model list.

Passed
Test details
This test ran 2 times; result: Passed.
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test details
This test ran 1 times; result: Passed.
Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.6K tokens
of which 192 tokens were billed at the cache price
连问 5 次，重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed
Test details
This test ran 5 times: 5 passed.
This test used 16.1K tokens
of which 8.7K tokens were billed at the cache price
32K 上下文能力实测

32K 长度的内容能稳定读完，这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 19.5K tokens
of which 192 tokens were billed at the cache price

Reviews

还没有人评论，来写第一条。

发表评论