grok-3Compare grok-3 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 3
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 3 面向通用语言任务,可以根据资料回答问题、解释概念、修改文字,也能协助理解代码和分析具体条件。写作时可要求它比较几种叙述角度,开发时可让它解释函数行为,学习时则可以用例子检查自己是否理解一个概念。
给出背景和目标读者有助于得到更合适的答案。例如同一份技术说明,给开发者看需要接口细节,给客户看则应说明用途与操作。把必须保留的信息、语气和篇幅写清,再让模型改写,能减少文风变化时丢失关键条件。
把原文直接提供给模型,并要求区分材料事实、合理推断和缺失信息。比较方案时明确评价维度,代码问题则附上运行环境、输入和预期行为。需要最新信息时,应提供近期资料,或通过实际启用的搜索工具获取,普通问答不会自动证明信息仍然有效。
xAI 官方 API 已将 grok-3 的请求重定向到 Grok 4.3。不同接入渠道的处理可能不同,需要复现历史结果时,应确认实际返回的模型信息并保存请求条件。持续使用旧名称的应用,也应重新检查输出风格和参数行为。
对代码和计算结果,可要求提供可运行示例或检查方法,再在实际环境验证;完整的文字解释并不代表程序已经执行成功。
例如提交一份面向客户的 API 错误说明,要求:“改写成清楚的中文帮助文档,保留错误码、触发条件和解决步骤。先解释用户能做什么,再列出需要联系支持的情况。不要把偶发错误写成永久故障,也不要补充材料中没有的恢复时间。”
代码任务可提供最小可复现片段,要求说明输入、输出和边界条件。保留原稿与请求,便于比较修改效果。需要跨时间复现时记录响应中的实际模型信息,并用固定样例检查旧名称重定向后是否影响应用。
/v1/chat/completions| Parameter | Type | Default / range | Description |
|---|---|---|---|
temperature | number | = 10 ~ 2 | Sampling temperature; lower is more deterministic |
top_p | number | = 10 ~ 1 | Nucleus sampling probability mass |
max_tokens | integer | >= 1 | Maximum number of tokens in the response |
frequency_penalty | number | = 0-2 ~ 2 | Penalises repetition of frequent tokens |
presence_penalty | number | = 0-2 ~ 2 | Encourages introducing new topics |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
n | integer | = 1>= 1 | Number of completions to generate |
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 |
logprobs | boolean | = false | Return per-token log probabilities |
top_logprobs | integer | 0 ~ 20 | Number of top log probabilities returned per token |
logit_bias | object | — | Per-token logit bias map |
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 |
|---|---|---|---|
temperature | number | = 10 ~ 2 | Sampling temperature; lower is more deterministic |
top_p | number | = 10 ~ 1 | Nucleus sampling probability mass |
max_tokens | integer | >= 1 | Maximum number of tokens in the response |
frequency_penalty | number | = 0-2 ~ 2 | Penalises repetition of frequent tokens |
presence_penalty | number | = 0-2 ~ 2 | Encourages introducing new topics |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
n | integer | = 1>= 1 | Number of completions to generate |
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 |
logprobs | boolean | = false | Return per-token log probabilities |
top_logprobs | integer | 0 ~ 20 | Number of top log probabilities returned per token |
logit_bias | object | — | Per-token logit bias map |
user | string | — | End-user identifier for abuse monitoring |
| Supplier | RPM | TPM | RPD |
|---|---|---|---|
| xAI | Unlimited | Unlimited | Unlimited |
No restriction
Compare grok-3 API pricing, supported endpoints, capabilities and access options on Modelsell.
Create an API key with access to grok-3, 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.
Start with the use cases and prompting guidance on this page, then evaluate the model with representative inputs from your project.
