Grok 4 Fast now has 2M context window

Requests which make use of xAI provided server-side tools are priced based on two components: token usage and server-side tool invocations. Since the agent autonomously decides how many tools to call, costs scale with query complexity.

Token Costs

All standard token types are billed at the rate for the model used in the request:

• Input tokens: Your query and conversation history
• Reasoning tokens: Agent's internal thinking and planning
• Completion tokens: The final response
• Image tokens: Visual content analysis (when applicable)
• Cached prompt tokens: Prompt tokens that were served from cache rather than recomputed

Tool Invocation Costs

For the view image and view x video tools, you will not be charged for the tool invocation itself but will be charged for the image tokens used to process the image or video.

For Remote MCP tools, you will not be charged for the tool invocation but will be charged for any tokens used.

For more information on using Tools, please visit our guide on Tools.

Live Search Pricing

Live Search costs $25 per 1,000 sources requested, each source used (Web, X, News, RSS) in a request counts toward the usage. That means a search using 4 sources costs $0.10 while a search using 1 source is $0.025. A source (e.g. Web) may return multiple citations, but you will be charged for only one source.

The number of sources used can be found in the response object, which contains a field called response.usage.num_sources_used.

For more information on using Live Search, visit our guide on Live Search or look for search_parameters parameter on API Reference - Chat Completions.

Documents Search Pricing

For users using our Collections API and Documents Search, the following pricing applies:

Usage Guidelines Violation Fee

A rare occurrence for most users, when your request is deemed to be in violation of our usage guideline by our system, we will charge a $0.05 per request usage guidelines violation fee.

Additional Information Regarding Models

• No access to realtime events without Live Search 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, please use Live Search function, or pass any realtime data as context in your system prompt.
• Chat models
  • No role order limitation: You can mix system, user, or assistant roles in any sequence for your conversation context.
• 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)

Model Aliases

Some models have aliases to help user 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.

Billing and Availability

Your model access might vary depending on various factors such as geographical location, account limitations, etc.

For how the bills are charged, visit Manage Billing for more information.

For the most up-to-date information on your team's model availability, visit Models Page on xAI Console.

Model Input and Output

Each model can have one or multiple input and output capabilities. The input capabilities refer to which type(s) of prompt can the model accept in the request message body. The output capabilities refer to which type(s) of completion will the model generate in the response message body.

This is a prompt example for models with text input capability:

This is a prompt example for models with text and image input capabilities:

This is a prompt example for models with text input and image output capabilities:

Context Window

The context window determines the maximum amount of token accepted by the model in the prompt.

For more information on how token is counted, visit Consumption and Rate Limits.

If you are sending the entire conversation history in the prompt for use cases like chat assistant, the sum of all the prompts in your conversation history must be no greater than the context window.

Cached prompt tokens

Trying to run the same prompt multiple times? You can now use cached prompt tokens to incur less cost on repeated prompts. By reusing stored prompt data, you save on processing expenses for identical requests. Enable caching in your settings and start saving today!

The caching is automatically enabled for all requests without user input. You can view the cached prompt token consumption in the "usage" object.

For details on the pricing, please refer to the pricing table above, or on xAI Console.