grok-4.20-0309-non-reasoningCompare grok-4.20-0309-non-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 Non 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 Non-Reasoning 可以阅读文字和图片,并用文字或结构化格式返回结果。它适合根据界面截图解释操作、从图文资料中提取字段,或按照明确规则整理输入,便于应用继续处理。需要直接答复、任务条件比较清楚时,可以从这种模式开始。
例如用户提交一张设置页截图,可以让模型指出可见选项、解释当前状态,并回答下一步应该在哪里操作。整理商品资料时,也可以同时提供说明文字与图片,提取名称、规格描述和可见信息;对看不清或未出现的字段保留空值,避免自动补全。
它支持结构化输出,可以在支持该功能的接口中定义 JSON Schema,明确字段类型、必填项与允许值。固定结构有助于后续校验,但不代表字段内容天然正确。应用仍应检查日期、数值范围,以及每个字段是否有输入依据。
通过函数调用,可连接应用提供的查询工具,例如知识库或业务接口。让模型先提取查询条件,再将真实查询结果组织成回复。工具由应用实际执行;没有返回值时,不能把猜测当作查询结果。
处理长资料时,给材料分配编号,把当前问题放在清楚的位置。图片中的小字应尽量清晰,必要时补充局部截图。复杂计算或多步论证可以交给推理版本,日常信息提取则应优先把字段和缺失值规则写清。
上传设置页截图后可以输入:
“请只依据截图提取每个可见设置项,返回 name、current_value、is_enabled、evidence 四个字段;看不清的值写 null。随后用两句话解释当前配置,不猜测折叠区域里的内容。”
需要稳定 JSON 时,在请求中配置对应 Schema,而不是只要求‘输出 JSON’。先检查字段能否对应截图,再连接后续查询工具。处理多张图时为图片编号,并说明它们是同一页面的不同区域还是不同页面,避免将信息错误合并。
/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-non-reasoning API pricing, supported endpoints, capabilities and access options on Modelsell.
Create an API key with access to grok-4.20-0309-non-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.
