Verification report details

Is grok-4.5 genuine? Deep check result

Report ID MZZR202609031055390D5C59Generated at 2026/09/03 18:55

Matched with issues

grok-4.5 本次深度验真结果:Matched但Matched with issues(76/100)。主要问题:复杂推理题答得不稳;接口返回的格式不规范。

76Model consistency score

主要问题:复杂推理题答得不稳;接口返回的格式不规范。

Tested byMozhenzhen
Tested modelGrok 4.5
Providers95ai
Requests37
Duration6 min 13 sec
Identity verdictVerified
Reference禾维

Token usage check

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

Reported usage66.7KThe actual usage reported by the API; this page goes by it.Estimated usage74.9KEstimated from this test's requests.Deviation11% 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 rate81.3%
Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run17.3KCached tokens14.1KNon-cached tokens3.2KAverage per run3.5K
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 次:缓存占比 83.3%,缓存 2.8K token,本次用量 3.4K token83.3%1times第 2 次:缓存占比 87.3%,缓存 2.8K token,本次用量 3.2K token87.3%2times第 3 次:缓存占比 87.4%,缓存 2.8K token,本次用量 3.2K token87.4%3times第 4 次:缓存占比 77.2%,缓存 2.8K token,本次用量 3.6K token77.2%4times第 5 次:缓存占比 73.5%,缓存 2.8K token,本次用量 3.8K token73.5%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

Matched with issues76/100

主要问题:复杂推理题答得不稳;接口返回的格式不规范。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly5 / 12
接口返回的格式不规范(让它调用工具,返回格式对不对) -7
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model15 / 25
复杂推理题答得不稳(逻辑网格推理) -10
Is usage and billing reasonable10 / 10
No deductions
Will it keep working18 / 25
复杂推理题答得不稳(逻辑网格推理) -4接口返回的格式不规范(让它调用工具,返回格式对不对) -3

Test details

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

21 checks
Model list visibility

grok-4.5 is visible in the API model list.

Passed
Test details
This test ran 12 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.1K 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 462 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.7K 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 719 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 1.3K 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 2.4K tokens
of which 256 tokens were billed at the cache price
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 553 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: Logic-grid reasoning was unstable
This test used 7.3K tokens
of which 192 tokens were billed at the cache price
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。

Passed
Test details
This test ran 2 times: 2 passed.
This test used 1.2K 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.8K tokens
of which 256 tokens were billed at the cache price
Grok / xAI

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 2.2K 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 952 tokens
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.5K tokens
of which 256 tokens were billed at the cache price
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 2.0K 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 589 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: Protocol structure was unstable
让它按指定格式输出,格式兑现了吗

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 841 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 17.3K tokens
of which 14.1K 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.6K 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? Deep check result

Report ID:MZZR202609031055390D5C59Generated at:2026/09/03 18:55
Provider detailsAI model details
Model consistency score

Matched with issues

grok-4.5 本次深度验真结果:Matched但Matched with issues(76/100)。主要问题:复杂推理题答得不稳;接口返回的格式不规范。

Tested byMozhenzhen
Tested modelGrok 4.5
Providers95ai
Requests37
Duration6 min
Identity verdictVerified
Reference禾维

Token usage check

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

Reported usage66.7KThe actual usage reported by the API; this page goes by it.Estimated usage74.9KEstimated from this test's requests.Deviation11% 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 rate81.3%
Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run17.3KCached tokens14.1KNon-cached tokens3.2KAverage per run3.5K
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 次:缓存占比 83.3%,缓存 2.8K token,本次用量 3.4K token83.3%1times第 2 次:缓存占比 87.3%,缓存 2.8K token,本次用量 3.2K token87.3%2times第 3 次:缓存占比 87.4%,缓存 2.8K token,本次用量 3.2K token87.4%3times第 4 次:缓存占比 77.2%,缓存 2.8K token,本次用量 3.6K token77.2%4times第 5 次:缓存占比 73.5%,缓存 2.8K token,本次用量 3.8K token73.5%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

Matched with issues76/100

主要问题:复杂推理题答得不稳;接口返回的格式不规范。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly5 / 12
接口返回的格式不规范(让它调用工具,返回格式对不对) -7
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model15 / 25
复杂推理题答得不稳(逻辑网格推理) -10
Is usage and billing reasonable10 / 10
No deductions
Will it keep working18 / 25
复杂推理题答得不稳(逻辑网格推理) -4接口返回的格式不规范(让它调用工具,返回格式对不对) -3

Test details

Expand any row for details; anything private has been removed

21 checks
Model list visibility

grok-4.5 is visible in the API model list.

Passed
Test details
This test ran 12 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.1K 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 462 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.7K 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 719 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 1.3K 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 2.4K tokens
of which 256 tokens were billed at the cache price
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 553 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: Logic-grid reasoning was unstable
This test used 7.3K tokens
of which 192 tokens were billed at the cache price
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。

Passed
Test details
This test ran 2 times: 2 passed.
This test used 1.2K 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.8K tokens
of which 256 tokens were billed at the cache price
Grok / xAI

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 2.2K 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 952 tokens
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.5K tokens
of which 256 tokens were billed at the cache price
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 2.0K 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 589 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: Protocol structure was unstable
让它按指定格式输出,格式兑现了吗

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 841 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 17.3K tokens
of which 14.1K 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.6K tokens
of which 192 tokens were billed at the cache price

Reviews

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

发表评论