Grok 4.6 (batch) API: toman pricing and code
x-ai/grok-4.6:batch
You are billed for the usage the request actually reported. Prices follow the market. Cached input: 138,488 toman per 1M tokens. Web search: 1,731.10 toman per request.Pricing and top-ups
Grok 4.6 (batch) example: reading an image into JSON
The example is picked from this model's own capabilities. Drop in your key and it runs as is.
# tip: a data URI works too — base64 the file and prefix it with data:image/jpeg;base64,
curl https://api.uttapen.ir/v1/chat/completions \
-H "Authorization: Bearer sk-up-…" \
-H "Content-Type: application/json" \
-d '{
"model": "x-ai/grok-4.6:batch",
"messages": [{
"role": "user",
"content": [
{"type": "text", "text": "Return only the invoice number and the total, as JSON."},
{"type": "image_url", "image_url": {"url": "https://example.com/factor.jpg"}}
]
}]
}'import base64, json
from openai import OpenAI
client = OpenAI(base_url="https://api.uttapen.ir/v1", api_key="sk-up-…")
img = base64.b64encode(open("factor.jpg", "rb").read()).decode()
resp = client.chat.completions.create(
model="x-ai/grok-4.6:batch",
messages=[{
"role": "user",
"content": [
{"type": "text", "text": "Return the invoice number, the date and the total as JSON."},
{"type": "image_url", "image_url": {"url": f"data:image/jpeg;base64,{img}"}},
],
}],
response_format={"type": "json_object"},
)
print(json.loads(resp.choices[0].message.content))import OpenAI from "openai";
import { readFileSync } from "node:fs";
const client = new OpenAI({ baseURL: "https://api.uttapen.ir/v1", apiKey: "sk-up-…" });
const img = readFileSync("factor.jpg").toString("base64");
const resp = await client.chat.completions.create({
model: "x-ai/grok-4.6:batch",
messages: [{
role: "user",
content: [
{ type: "text", text: "Return the invoice number, the date and the total as JSON." },
{ type: "image_url", image_url: { url: `data:image/jpeg;base64,${img}` } },
],
}],
response_format: { type: "json_object" },
});
console.log(JSON.parse(resp.choices[0].message.content));What is Grok 4.6 (batch) good for?
Grok 4.6 (batch) is one of xAI's models. Put "x-ai/
What it can do beyond plain text: it reads images directly, which makes it a real option for invoices, forms and screenshots; it takes files such as PDFs as input; it supports tool calling, so it can invoke your own functions with valid arguments; it returns schema-valid JSON through response_format, ready to hand to your code; it has a reasoning mode that pays off on multi-step problems, maths and debugging. All of it works through the standard parameters of the official OpenAI SDK — no custom client, no wrapper. Keep in mind that reasoning tokens are output tokens and do appear on the bill.
Pricing is 553,951 toman per 1M input tokens and 1,661,853 per 1M output tokens. A 1,000-word round trip on Grok 4.6 (batch) lands near 2,881 toman. It supports cached input: repeated context is billed at 138,488 toman per 1M, which matters a lot if your system prompt is long. You are always charged for the usage the request actually reported, never for the estimate, and a failed request costs nothing.
The closest alternative with the same capabilities from a different provider is Claude Haiku 4.5: Grok 4.6 (batch) works out about 10% more expensive, and its context window is larger. Both run on the same key and the same code, so trying the other one is a single string change.
To make the figure concrete: 100,000 toman of credit buys roughly 35 thousand-word requests on Grok 4.6 (batch), and every 1,000 toman is about 347 words of round trip. A job with one million input tokens and one million output tokens comes to 2,215,804 toman in total. Filling this model's 500,000-token window costs 276,975 toman on the input side alone, which is the real reason to keep conversation history short.
This id gets confused with "x-ai/
xAI has 11 models in our catalogue; the cheapest is Grok 4.3 (batch) at 1,350 toman per thousand words and the dearest Grok Latest at 3,601. Among the less common parameters it accepts logprobs, reasoning_effort, top_logprobs — all through the standard request body. By context size the nearest option from another provider is Dots3-Note Preview (free) at 512,000 tokens.
Good fits: product chatbots and internal assistants, where cost and quality have to balance, logic puzzles and code review, pulling text and fields out of images, agents that reach out to APIs and databases, extracting data against a fixed schema, analysing a long document or codebase in one request.
Grok 4.6 is a model from SpaceXAI with frontier performance on coding, knowledge work, and STEM. It is succeeded by [Grok 4.7](/x-ai/grok-4.7).
Three real jobs, priced on this model
Each figure is derived from the prices above and moves when they do.
| Job | Tokens | Cost |
|---|---|---|
| One chat turn with a medium history | 1,500 in + 400 out | 1,496 toman |
| Summarising a ten-page document | 4,000 in + 600 out | 3,213 toman |
| Classifying a thousand short rows | 120,000 in + 20,000 out | 99,711 toman |
Other variants of this model
Same core model, different execution terms and different price. This page is the batch variant.
| Variant | Model id | Output / 1M | Context |
|---|---|---|---|
| standard | x-ai/grok-4.6 | 2,077,316 | 500,000 |
Put the variant's id verbatim in the model field; nothing else in your code changes.
Frequently asked
- How do I call Grok 4.6 (batch) from Iran?
- Sign up with your mobile number, top the wallet up in toman, create an API key, then in the official OpenAI SDK point base_url at https:/
/ api.uttapen.ir/ v1 and set model to "x-ai/ grok-4.6:batch". Nothing else in your code changes. - What does Grok 4.6 (batch) cost in toman?
- 553,951 toman per 1M input tokens and 1,661,853 toman per 1M output tokens; a 1,000-word request is around 2,881 toman. You pay for the usage that request actually reported, and a failed request costs nothing.
- How much input does Grok 4.6 (batch) take?
- Up to 500,000 tokens per request, roughly 375k words. A single answer can reach 450,000 tokens.
- Does Grok 4.6 (batch) support streaming and tool calling?
- Streaming (stream=true) works on every model here. This one supports tool calling in the standard OpenAI shape. Image input is accepted through image_url, as a data URI or a public URL. Structured output through response_format works too.