Verification report details

Is grok-4.5 genuine? Standard check result

Report ID MZZR2026081513544674CE7CGenerated at 2026/08/15 21:54

Matched

grok-4.5 本次标准验真结果:Matched(91/100)。主要问题:问到不该说的内容时把握不住分寸。

91Model consistency score

主要问题:问到不该说的内容时把握不住分寸。

Tested byMozhenzhen
Tested modelGrok 4.5
Providersa6api
Requests21
Duration2 min 55 sec
Identity verdictVerified
Reference禾维

Token usage check

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

Reported usage49.6KThe actual usage reported by the API; this page goes by it.Estimated usage74.0KEstimated from this test's requests.Deviation33% 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 rate69.6%
Low cache share

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

Usage this run16.5KCached tokens11.5KNon-cached tokens5.0KAverage per run3.3K
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 次:缓存占比 6.0%,缓存 192 token,本次用量 3.2K token6.0%1times第 2 次:缓存占比 85.3%,缓存 2.8K token,本次用量 3.3K token85.3%2times第 3 次:缓存占比 85.3%,缓存 2.8K token,本次用量 3.3K token85.3%3times第 4 次:缓存占比 84.8%,缓存 2.8K token,本次用量 3.3K token84.8%4times第 5 次:缓存占比 84.7%,缓存 2.8K token,本次用量 3.3K token84.7%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

Matched91/100

主要问题:问到不该说的内容时把握不住分寸。

Can you call it, and is the model listed15 / 15
No deductions
Does the API respond properly15 / 15
No deductions
Is it the model it claims to be20 / 20
No deductions
Does it answer like the official model14 / 20
问到不该说的内容时把握不住分寸(隐藏提示词边界) -6
Is usage and billing reasonable15 / 15
No deductions
Will it keep working12 / 15
问到不该说的内容时把握不住分寸(隐藏提示词边界) -3

Test details

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

17 checks
Model list visibility

grok-4.5 is visible in the API model list.

Passed
Test details
This test ran 1 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 754 tokens
of which 384 tokens were billed at the cache price
指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 840 tokens
of which 192 tokens were billed at the cache price
JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.3K tokens
of which 192 tokens were billed at the cache price
标签结构复述

按官方接口的标准调用,看返回是否规范。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 600 tokens
of which 192 tokens were billed at the cache price
隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Hidden-prompt boundary was unclear
This test used 1.6K tokens
of which 192 tokens were billed at the cache price
品牌边界

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 610 tokens
of which 384 tokens were billed at the cache price
用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 606 tokens
of which 192 tokens were billed at the cache price
Grok / xAI

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.4K tokens
of which 192 tokens were billed at the cache price
模型代码锚定

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.1K tokens
of which 192 tokens were billed at the cache price
Model-family test: series and tier 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.9K tokens
of which 192 tokens were billed at the cache price
边打字边回和一次性回,结果一样吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 452 tokens
of which 192 tokens were billed at the cache price
让它调用工具,返回格式对不对

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 699 tokens
of which 384 tokens were billed at the cache price
让它按指定格式输出,格式兑现了吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 1 次都对。

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

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 16.5K tokens
of which 11.5K 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

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

发表评论

MozhenzhenBefore you buy AI, check Mozhenzhen
Scan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls

Is grok-4.5 genuine? Standard check result

Report ID:MZZR2026081513544674CE7CGenerated at:2026/08/15 21:54
Provider detailsAI model details
Model consistency score

Matched

grok-4.5 本次标准验真结果:Matched(91/100)。主要问题:问到不该说的内容时把握不住分寸。

Tested byMozhenzhen
Tested modelGrok 4.5
Providersa6api
Requests21
Duration3 min
Identity verdictVerified
Reference禾维

Token usage check

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

Reported usage49.6KThe actual usage reported by the API; this page goes by it.Estimated usage74.0KEstimated from this test's requests.Deviation33% 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 rate69.6%
Low cache share

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

Usage this run16.5KCached tokens11.5KNon-cached tokens5.0KAverage per run3.3K
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 次:缓存占比 6.0%,缓存 192 token,本次用量 3.2K token6.0%1times第 2 次:缓存占比 85.3%,缓存 2.8K token,本次用量 3.3K token85.3%2times第 3 次:缓存占比 85.3%,缓存 2.8K token,本次用量 3.3K token85.3%3times第 4 次:缓存占比 84.8%,缓存 2.8K token,本次用量 3.3K token84.8%4times第 5 次:缓存占比 84.7%,缓存 2.8K token,本次用量 3.3K token84.7%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

Matched91/100

主要问题:问到不该说的内容时把握不住分寸。

Can you call it, and is the model listed15 / 15
No deductions
Does the API respond properly15 / 15
No deductions
Is it the model it claims to be20 / 20
No deductions
Does it answer like the official model14 / 20
问到不该说的内容时把握不住分寸(隐藏提示词边界) -6
Is usage and billing reasonable15 / 15
No deductions
Will it keep working12 / 15
问到不该说的内容时把握不住分寸(隐藏提示词边界) -3

Test details

Expand any row for details; anything private has been removed

17 checks
Model list visibility

grok-4.5 is visible in the API model list.

Passed
Test details
This test ran 1 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 754 tokens
of which 384 tokens were billed at the cache price
指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 840 tokens
of which 192 tokens were billed at the cache price
JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.3K tokens
of which 192 tokens were billed at the cache price
标签结构复述

按官方接口的标准调用,看返回是否规范。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 600 tokens
of which 192 tokens were billed at the cache price
隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 有几次没对上。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Hidden-prompt boundary was unclear
This test used 1.6K tokens
of which 192 tokens were billed at the cache price
品牌边界

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 610 tokens
of which 384 tokens were billed at the cache price
用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 606 tokens
of which 192 tokens were billed at the cache price
Grok / xAI

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.4K tokens
of which 192 tokens were billed at the cache price
模型代码锚定

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.1K tokens
of which 192 tokens were billed at the cache price
Model-family test: series and tier 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.9K tokens
of which 192 tokens were billed at the cache price
边打字边回和一次性回,结果一样吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 452 tokens
of which 192 tokens were billed at the cache price
让它调用工具,返回格式对不对

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 699 tokens
of which 384 tokens were billed at the cache price
让它按指定格式输出,格式兑现了吗

对照官方公开的产品说明来测。针对这个模型再做一项专门检测。 1 次都对。

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

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

Passed
Test details
This test ran 5 times: 5 passed.
This test used 16.5K tokens
of which 11.5K 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

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

发表评论