Grok Build 0.1

New
grok-build-0.1

Our coding model — trained specifically for agentic coding workflows. Use Grok Build for code.

View model
Context256k tokens
Input$1.00 / 1M tokens
Output$2.00 / 1M tokens

Grok 4.3

grok-4.3

For everything except code, audio, image, and video. The most intelligent and fastest model we’ve built.

Context1 million tokens
Input$1.25 / 1M tokens
Output$2.50 / 1M tokens
ReasoningConfigurable
View model

Voice API

Real-time conversations, speech-to-text, and text-to-speech.

Agent$3.00 / hour
TTS$15.00 / 1M chars
STT (Batch)$0.10 / hour
STT (Streaming)$0.20 / hour

Imagine API

Turn ideas into reality with image and video generation.

ModesGeneration & editing
SpeedIndustry-leading
Image · 1K / 2K$0.02 / image
Video · 480p / 720p / 1080p$0.05 / sec

Which model should I choose?

Your choice depends on your use case. We have dedicated models and APIs for code, audio, image, and video capabilities. For code, use Grok Build — it is our coding model. For everything else, use Grok 4.3. It is the most intelligent and fastest model we’ve built.

Additional Information Regarding Models

  • No access to realtime events without search tools enabled
    • Grok has no knowledge of current events or data beyond what was present in its training data.
    • To incorporate realtime data with your request, enable server-side search tools (Web Search / X Search). See Web Search and X Search.
  • Chat models
    • No role order limitation: You can mix system, user, or assistant roles in any sequence for your conversation context.
    • logprobs and top_logprobs are not supported by models grok-4.20 and newer. These fields will be silently ignored if set.
  • Image input models
    • Maximum image size: 20MiB
    • Maximum number of images: No limit
    • Supported image file types: jpg/jpeg or png.
    • Any image/text input order is accepted (e.g. text prompt can precede image prompt)

The knowledge cut-off date of Grok 3 and Grok 4 is November, 2024.


Model Aliases

Some models have aliases to help users automatically migrate to the next version of the same model. In general:

  • <modelname> is aliased to the latest stable version.
  • <modelname>-latest is aliased to the latest version. This is suitable for users who want to access the latest features.
  • <modelname>-<date> refers directly to a specific model release. This will not be updated and is for workflows that demand consistency.

For most users, the aliased <modelname> or <modelname>-latest are recommended, as you would receive the latest features automatically.


Last updated: May 29, 2026