grok-4.20-0309-reasoningCompare grok-4.20-0309-reasoning API pricing, supported endpoints, capabilities and access options on Modelsell.
Grok tokenizer (BPE)Scores on standardized evaluations. Higher percentages are better — and rank percentile shows
Metrics sourced fromArtificial Analysis 2026-09-30·Grok 4.20 0309 Reasoning
This model is not included in the current benchmark snapshot.
Missing models or measurements are not zero scores.
Benchmark charts preserve the source model selection and reasoning settings. Missing models or measurements are not zero scores, and benchmark cost or speed is not this site’s service commitment.
Grok 4.20 Reasoning 可以同时处理文字与图片,在作答前进行推理,适合需求检查、图表分析和多资料对照。例如把页面截图与产品验收要求一起提供,让它检查可见状态是否符合规则;把图表和指标定义放在一起,让它解释趋势,并指出无法仅凭图形确定的原因。
处理较长材料时,它可以结合前后的约束来回答具体问题。可以给需求、设计说明和测试记录分别编号,让模型按同一个检查标准查找冲突。与一次泛泛的总结相比,要求它逐项说明“满足什么、依据在哪、还缺什么”,更容易得到可以继续处理的结果。
让模型把图片中直接可见的内容、文字材料给定的规则和由此得到的判断分开。对于被遮挡的区域、小字和无法从静态截图确认的交互,应保留不确定状态。要分析页面行为,可补充操作前后的截图和复现步骤。
它支持函数调用,可以根据分析结果请求应用提供的查询工具,再利用返回信息继续判断。实际查询或执行由工具完成,不能用生成的描述代替执行结果。需要固定输出时,可使用结构化输出功能定义字段,让每项检查包含结论、证据和待补充信息。
推理有助于处理复杂约束,重要结论仍要有验证方法。对代码运行测试,对数值核对公式,对图片判断回看原图;要求模型给出简明依据与可验证步骤,便于人工或程序检查。
上传结算页截图并附上验收要求后,可以输入:
“请逐项检查优惠、运费与总价的展示是否符合下方规则。区分截图可见事实和推断,输出 requirement_id、status、evidence、missing_information。看不到的内容标为无法确认,不推测点击后的行为。规则:{验收清单}。”
先检查模型是否读对金额与文字,再核对规则判断。提供操作前后两张图时,说明各自对应的状态。若还需查询订单或运行测试,向应用接入相应工具,将真实结果回传后再生成最终检查清单。
/v1/chat/completions| Parameter | Type | Default / range | Description |
|---|---|---|---|
reasoning_effort | enum | = medium | Controls how much the model thinks before answering |
max_completion_tokens | integer | >= 1 | Maximum tokens including hidden reasoning tokens |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
stream | boolean | = false | Stream tokens via Server-Sent Events |
response_format | object | — | Force JSON object or schema-conforming output |
tools | array | — | Tool / function declarations the model may call |
tool_choice | string | autononerequired | Tool-choice policy or specific tool name |
user | string | — | End-user identifier for abuse monitoring |
Replace <YOUR_API_KEY> with the API key from your token settings.
All requests must include Authorization: Bearer <TOKEN> header. Anthropic-formatted endpoints accept the x-api-key header instead.
Generate tokens from the Tokens page; you can scope them to specific models, groups, IPs, and rate-limits.
| Parameter | Type | Default / range | Description |
|---|---|---|---|
reasoning_effort | enum | = medium | Controls how much the model thinks before answering |
max_completion_tokens | integer | >= 1 | Maximum tokens including hidden reasoning tokens |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
stream | boolean | = false | Stream tokens via Server-Sent Events |
response_format | object | — | Force JSON object or schema-conforming output |
tools | array | — | Tool / function declarations the model may call |
tool_choice | string | autononerequired | Tool-choice policy or specific tool name |
user | string | — | End-user identifier for abuse monitoring |
| Supplier | RPM | TPM | RPD |
|---|---|---|---|
| xAI | Unlimited | Unlimited | Unlimited |
No restriction
Compare grok-4.20-0309-reasoning API pricing, supported endpoints, capabilities and access options on Modelsell.
Create an API key with access to grok-4.20-0309-reasoning, then use the exact model ID and a supported endpoint from the API access section. Request fields depend on the selected endpoint.
Pricing depends on the selected provider group and the model billing unit. The current input, output, request, or media prices are shown on this page before sign-up.
The model catalog lists a context window of 1000000 tokens. Check the selected endpoint for request limits.
Start with the use cases and prompting guidance on this page, then evaluate the model with representative inputs from your project.
