Grok Build 0.1 API: toman pricing and code
x-ai/grok-build-0.1
visiontoolsreasoningjsonfilesYou are billed for the usage the request actually reported. Prices follow the market. Cached input: 58,025 toman / 1M. Web search: 1,450.63 toman / request.Pricing and top-ups
Grok Build 0.1 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-build-0.1",
"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-build-0.1",
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-build-0.1",
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 Build 0.1 good for?
xAI publishes this model; we expose it under the id "x-ai/grok-build-0.1". Its context window is 256,000 tokens, roughly 192k English words in one request. A single response can run to 230,400 tokens. On price it sits in the "cheap" band — cheaper than 200 and dearer than 206 of the other paid models in the catalogue.
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 290,125 toman per 1M input tokens and 580,250 per 1M output tokens. A 1,000-word round trip on Grok Build 0.1 lands near 1,131 toman. It supports cached input: repeated context is billed at 58,025 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 Seed 1.6: Grok Build 0.1 works out roughly 1.3× more expensive, and its context window is smaller. 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 88 thousand-word requests on Grok Build 0.1, and every 1,000 toman is about 884 words of round trip. A job with one million input tokens and one million output tokens comes to 870,375 toman in total. Filling this model's 256,000-token window costs 74,272 toman on the input side alone, which is the real reason to keep conversation history short.
Its nearest relative in the catalogue is "x-ai/grok-4.5", and choosing between those two is where most people hesitate. On a thousand-word request this variant works out 2.7× cheaper (1,131 against 3,017 toman). The context windows differ too: 256,000 against 500,000 tokens. Maximum answer length differs as well: 230,400 against 450,000 tokens. On parameters the other takes reasoning_effort.
xAI has 8 models in our catalogue; the cheapest is Grok 4.3 (batch) at 1,131 toman per thousand words and the dearest Grok Latest at 3,017. Among the less common parameters it accepts logprobs, top_logprobs — all through the standard request body. By context size the nearest option from another provider is Command A at 256,000 tokens.
Good fits: high-volume work such as classification, tagging and bulk summarising, 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 Build 0.1 is SpaceXAI’s fast coding model trained specifically for agentic software engineering workflows. It supports text and image inputs with text output, and is optimized for interactive coding...
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 | 667 toman |
| Summarising a ten-page document | 4,000 in + 600 out | 1,509 toman |
| Classifying a thousand short rows | 120,000 in + 20,000 out | 46,420 toman |
Frequently asked
- How do I call Grok Build 0.1 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-build-0.1". Nothing else in your code changes.
- What does Grok Build 0.1 cost in toman?
- 290,125 toman per 1M input tokens and 580,250 toman per 1M output tokens; a 1,000-word request is around 1,131 toman. You pay for the usage that request actually reported, and a failed request costs nothing.
- How much input does Grok Build 0.1 take?
- Up to 256,000 tokens per request, roughly 192k words. A single answer can reach 230,400 tokens.
- Does Grok Build 0.1 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.