Free model verification · Redacted public report

grok-4.5 standard verification model-consistency report

Report ID MZZR2026082618333422FAB5Generated at 2026/08/27 02:33

Matched

grok-4.5 standard verification result: Matched (90/100). Main deductions: Protocol structure was unstable.

90Consistency score

主要扣分项：协议结构不稳定。

EvaluatorMozhenzhen

Tested modelGrok 4.5

ProvidersMore Code 联盟

Samples126 probes

Duration3 min 54 sec

Verification versionV11

Identity verdictVerified

Verification basis禾维

Token usage

Measured API usage is shown first; official baselines or test estimates are used only when measured values are unavailable.

Measured token usage12.9KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate880Precisely estimated from this test suite when no official baseline is available.Variance assessment1362% aboveMeasured token usage is above the estimate; review billing or provider logs.Usage conclusionAbove estimateThis reflects usage observability, not the final billed amount.

Model authenticity score

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

Scoring breakdown

Matched90/100

主要扣分项：协议结构不稳定。

Callability and model visibility15 / 15

No deductions

Protocol and response structure8 / 15

协议结构不稳定（正式来源必检：专项：工具调用结构） -7

Identity and model match20 / 20

No deductions

能力题表现20 / 20

No deductions

Usage and billing consistency15 / 15

No deductions

稳定性与复测表现12 / 15

协议结构不稳定（正式来源必检：专项：工具调用结构） -3

Test details

Expand each check to view the redacted evidence notes.

15 checks

Model list visibility

grok-4.5 is visible in the API model list.

Passed

Test evidence

Check: Model list visibility
Status: Passed
Samples: 112
API path: /models
Visible models: 112

Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed

Test evidence

Check: Basic call probe
Status: Passed
Samples: 1
API path: /chat/completions

Quick test: model self-identification

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Quick test: model self-identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 560
Cached tokens: 128

Standard test: instruction following

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed

Test evidence

Check: Standard test: instruction following
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 827
Cached tokens: 192

Standard test: JSON structure

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed

Test evidence

Check: Standard test: JSON structure
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 1.6K

Standard test: tag-structure repetition

General test used as Mozhenzhen verification evidence for the protocol dimension. All samples passed.

Passed

Test evidence

Check: Standard test: tag-structure repetition
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 636
Cached tokens: 192

Standard test: hidden-prompt boundary

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed

Test evidence

Check: Standard test: hidden-prompt boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 1.5K
Cached tokens: 192

Standard test: brand boundary

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Standard test: brand boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 905
Cached tokens: 128

Standard test: usage observability

General test used as Mozhenzhen verification evidence for the usage dimension. All samples passed.

Passed

Test evidence

Check: Standard test: usage observability
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 572
Cached tokens: 128

品牌题：Grok / xAI 证据边界证据边界

Brand-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: 品牌题：Grok / xAI 证据边界 证据边界
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 2.8K
Cached tokens: 192

Model-specific test: model-code anchoring

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Model-specific test: model-code anchoring
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 550
Cached tokens: 128

Model-family test: series and tier identification

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Model-family test: series and tier identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 648
Cached tokens: 128

正式来源必检：专项：流式 / 非流式一致性

按禾维确定的方法执行。执行专项题，用于形成模真真验真证据。全部样本Passed。

Passed

Test evidence

Check: 正式来源必检：专项：流式 / 非流式一致性
Status: Passed
Samples: 1
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 302
Cached tokens: 128

正式来源必检：专项：工具调用结构

按禾维确定的方法执行。执行专项题，用于形成模真真验真证据。存在样本未完全Passed。

Needs review

Test evidence

Check: 正式来源必检：专项：工具调用结构
Status: Needs review
Samples: 1
Needs review原因：协议结构不稳定
Results: Passed 0 / Needs review 1 / Failed 0

正式来源必检：专项：JSON Schema 结构化输出

按禾维确定的方法执行。执行专项题，用于形成模真真验真证据。全部样本Passed。

Passed

Test evidence

Check: 正式来源必检：专项：JSON Schema 结构化输出
Status: Passed
Samples: 1
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 769
Cached tokens: 192

Report comments

No public reviews

Be the first to leave a review.

Post an anonymous comment

Rating

5 points

This reportReviews

Upload images/videoClick or drag to uploadUp to 9 images and 1 video · Sign-in required for attachments

AI service research and model verification report

Scan to view reportOpen full report

Free model verification · Supports all text models

grok-4.5 standard verification model-consistency report

Report ID:MZZR2026082618333422FAB5Generated at：2026/08/27 02:33

Provider details AI model details

Model consistency score

Matched

grok-4.5 standard verification result: Matched (90/100). Main deductions: Protocol structure was unstable.

EvaluatorMozhenzhen

Tested modelGrok 4.5

ProvidersMore Code 联盟

Samples126

Duration4 min

Test versionV11

Identity verdictVerified

Verification basis禾维

Token usage

Measured API usage is shown first; official baselines or test estimates are used only when measured values are unavailable.

Model authenticity score

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

Scoring breakdown

Matched90/100

主要扣分项：协议结构不稳定。

Callability and model visibility15 / 15

No deductions

Protocol and response structure8 / 15

协议结构不稳定（正式来源必检：专项：工具调用结构） -7

Identity and model match20 / 20

No deductions

能力题表现20 / 20

No deductions

Usage and billing consistency15 / 15

No deductions

稳定性与复测表现12 / 15

协议结构不稳定（正式来源必检：专项：工具调用结构） -3

Test details

Expand each check to view the redacted evidence notes.

15 checks

Model list visibility

grok-4.5 is visible in the API model list.

Passed

Test evidence

Check: Model list visibility
Status: Passed
Samples: 112
API path: /models
Visible models: 112

Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed

Test evidence

Check: Basic call probe
Status: Passed
Samples: 1
API path: /chat/completions

Quick test: model self-identification

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Quick test: model self-identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 560
Cached tokens: 128

Standard test: instruction following

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed

Test evidence

Check: Standard test: instruction following
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 827
Cached tokens: 192

Standard test: JSON structure

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed

Test evidence

Check: Standard test: JSON structure
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 1.6K

Standard test: tag-structure repetition

General test used as Mozhenzhen verification evidence for the protocol dimension. All samples passed.

Passed

Test evidence

Check: Standard test: tag-structure repetition
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 636
Cached tokens: 192

Standard test: hidden-prompt boundary

General test used as Mozhenzhen verification evidence for the ability dimension. All samples passed.

Passed

Test evidence

Check: Standard test: hidden-prompt boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 1.5K
Cached tokens: 192

Standard test: brand boundary

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Standard test: brand boundary
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 905
Cached tokens: 128

Standard test: usage observability

General test used as Mozhenzhen verification evidence for the usage dimension. All samples passed.

Passed

Test evidence

Check: Standard test: usage observability
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 572
Cached tokens: 128

品牌题：Grok / xAI 证据边界证据边界

Brand-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: 品牌题：Grok / xAI 证据边界 证据边界
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 2.8K
Cached tokens: 192

Model-specific test: model-code anchoring

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Model-specific test: model-code anchoring
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 550
Cached tokens: 128

Model-family test: series and tier identification

Model-specific test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed

Test evidence

Check: Model-family test: series and tier identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 648
Cached tokens: 128

正式来源必检：专项：流式 / 非流式一致性

按禾维确定的方法执行。执行专项题，用于形成模真真验真证据。全部样本Passed。

Passed

Test evidence

Check: 正式来源必检：专项：流式 / 非流式一致性
Status: Passed
Samples: 1
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 302
Cached tokens: 128

正式来源必检：专项：工具调用结构

按禾维确定的方法执行。执行专项题，用于形成模真真验真证据。存在样本未完全Passed。

Needs review

Test evidence

Check: 正式来源必检：专项：工具调用结构
Status: Needs review
Samples: 1
Needs review原因：协议结构不稳定
Results: Passed 0 / Needs review 1 / Failed 0

正式来源必检：专项：JSON Schema 结构化输出

按禾维确定的方法执行。执行专项题，用于形成模真真验真证据。全部样本Passed。

Passed

Test evidence

Check: 正式来源必检：专项：JSON Schema 结构化输出
Status: Passed
Samples: 1
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 769
Cached tokens: 192

Latest user reviews

No public reviews

Be the first to leave a review.

Comments and feedback on this report

Rating

5 points

This reportReviews

Upload images/videoClick or drag to uploadUp to 9 images and 1 video · Sign-in required for attachments