grok-build-0.1xAI
- endpoints
- 1
- regions
- 1
- api
- chat
- released
- May 2026
capabilities 4/8
| # | flags | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Global | 256K | $1.00 | $2.00 | $0.10 | zdr |
no measured traffic for this model yet. the endpoints table above carries provider pricing
no published benchmark scores for this model
grok-build-0.1requesty routes this id across every provider serving grok-build-0.1, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it
Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.
from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create( model="grok-build-0.1", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ],) print(response.choices[0].message.content)
Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models
Grok Build 0.1 is xAI's dedicated coding model optimized for software engineering tasks including code generation, review, debugging, and technical problem solving.
questions 6
Which providers serve grok-build-0.1?
How much does grok-build-0.1 cost?
Is grok-build-0.1 open weights?
What is the context window of grok-build-0.1?
How do I use grok-build-0.1 with the OpenAI SDK?
Should I call grok-build-0.1 by its managed id or a provider id?
more from xai 6
| model | context | from /M | providers |
|---|---|---|---|
| grok-4.6 | 500K | $2.00 | 1 |
| grok-4.5 | 500K | $2.00 | 1 |
| grok-4.3 | 1M | $1.25 | 1 |
| grok-4.2-beta | 2M | $2.00 | 1 |
| grok-4-1-fast-reasoning | 2M | $0.20 | 1 |
| grok-4-1-fast-non-reasoning | 2M | $0.20 | 1 |
route grok-build-0.1 through one endpoint
One key for 1 provider on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology
