Introducing Grok Bot 1.0. Bots can be shared and are more collaborative and capable than ever. https://t.co/gmxan7jupQ
Introducing Grok Bot 1.0. Bots can be shared and are more collaborative and capable than ever. https://t.co/gmxan7jupQ
Find model releases, free access and plan changes.
Requests to `grok-imagine-image-quality` and `grok-imagine-image-pro` are now served by `grok-imagine-image-2.0-low`: `grok-imagine-image-2.0` with `quality` set to `low`, at a lower per-image price. No request changes are needed. `usage.cost_in_usd_ticks` on each response reflects the lower price, and gRPC responses (xAI SDK) report `grok-imagine-image-2.0-low` as the `model`. See the [migration guide](/developers/migration/imagine-image-quality-nov-2).
You can now use Grok 4.1 Fast models with the agent tools, check out the [documentation of agent tools](/developers/tools/overview) to get started. The price of agent tools drops by up to 50% to no more than $5 per 1000 successful calls, see the new prices at [the pricing page](/developers/pricing#tools-pricing).
You can now upload files and use them in chat conversations with the Files API. For more details, check out [our guide on Files](/developers/files).
**Collections Search Tool**: You can now search through uploaded knowledge bases (collections) in chat conversations via the API. For more details, check out the [docs](/developers/tools/collections-search). **Remote MCP Tools**: You can now use tools from remote MCP servers in chat conversations via the API. For more details, check out the [docs](/developers/tools/remote-mcp). **Mixing client-side and server-side tools**: You can now mix client-side and server-side tools in the same chat conversation. For more details, check out the [docs](/developers/tools/advanced-usage#mixing-server-side-and-client-side-tools).
We are happy to announce the immediate availability of our API, which gives developers programmatic access to our Grok series of foundation models. To get started, head to [console.x.ai](https://console.x.ai/?utm_source=docs\&utm_medium=referral\&utm_campaign=developers-release-notes\&utm_content=console-home) and sign up to create an account. We are excited to see what developers build using Grok.
You can now set content guidelines on text API requests. Add a `guidelines` array to a Chat Completions or Responses API request to set how Grok handles content in the `nsfw`, `violence`, and `profanity` categories. Grok follows the guidelines as it writes its response. See [Custom Moderation Controls](/developers/advanced-api-usage/custom-moderation-controls).
`grok-voice-2.0` is deprecated. To upgrade, set `model` to `grok-voice-3.0` or `grok-voice-latest`, at the same price. See [Upgrading from Grok Voice 2.0](/developers/model-capabilities/audio/speech-to-speech#upgrading-from-grok-voice-20).
`grok-voice-transcribe-1.0` is deprecated and reaches end of life on October 2, 2026. All requests to that slug are routed to `grok-voice-transcribe-2.0` at the same price, with higher accuracy. See the [Speech to Text docs](/developers/model-capabilities/audio/speech-to-text).
New agentic server-side tools including `web_search`, `x_search`, and `code_execution` are available. For more details, check out [our guide on using Tools](/developers/tools/overview).
You can now send `safety_identifier`, an opaque end-user identifier assigned by your application, on Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC `GetCompletionsRequest`. It lets SpaceXSI attribute a policy violation to one of your end users rather than to your API key. The legacy `user` field is still accepted. See the [Security FAQ](/developers/faq/security#how-do-i-identify-which-of-my-end-users-caused-a-policy-violation).
On November 2, 2026, `grok-imagine-image-quality` is retired. Requests to the slug will be served by `grok-imagine-image-2.0` with `quality` set to `low`, with no change to the request or response shape and at a lower per-image price. `grok-imagine-image` (1.0) is not affected. See the [migration guide](/developers/migration/imagine-image-quality-nov-2).
You can now use our stateful Responses API to process requests.
**Auto quality.** The `quality` parameter on `grok-imagine-image-2.0` now accepts `auto`, and the default when `quality` is omitted has moved from `medium` to `auto`. Auto currently uses `low` for image generation and `medium` for image editing. Images are billed at the quality they are served at. Pass `low` or `medium` explicitly to pin a specific quality. See [Image Generation](/developers/model-capabilities/images/generation#quality). **Five reference images.** Image editing now accepts up to 5 source images per request (was 3). See [Multi-Image Editing](/developers/model-capabilities/images/multi-image-editing). **New aspect ratios.** Image generation and editing accept `21:9` (cinematic widescreen) and `5:2` (wide banners). See [Image Generation](/developers/model-capabilities/images/
You can upload files, create embeddings, and use them for inference with our Collections API.
`grok-imagine-video-1.5` now supports text-to-video, image-to-video, and reference-to-video (including optional preset voices), with native 1080p for T2V and I2V. Text-to-video on this model runs as text-to-image then image-to-video under the hood. See [Video Generation](/developers/model-capabilities/video/generation), [Image-to-Video](/developers/model-capabilities/video/image-to-video), and [Reference-to-Video](/developers/model-capabilities/video/reference-to-video).
Speech to Text now accepts a `vad_threshold` parameter (streaming query param and batch multipart field) to tune the voice-activity gate that skips non-speech audio. Lower values transcribe quieter or noisier speech — useful for narrowband telephony — and `0` disables the gate. See the [Speech to Text docs](/developers/model-capabilities/audio/speech-to-text).
You can now use Grok 4 via our API or on https://grok.com.
You can now request higher scheduling priority per request by setting `service_tier: "priority"` on text inference endpoints (Chat Completions and Responses). The response's `service_tier` field reports the tier actually applied, and priority rates are billed only when priority is used. For more details, see the [Priority Processing docs](/developers/advanced-api-usage/priority-processing).
**Public URLs for Files** — turn any file in your [Files API](/developers/files) storage into a permanent, unauthenticated URL that anyone can open, embed, or share. Revocable at any time, or set an auto-expiry between 1 hour and 30 days. See the [Public URLs docs](/developers/files/public-urls). **Reference stored files as image & video inputs** — substitute `image_file_id`, `video_file_id`, or `reference_image_file_ids` for URL inputs across every image & video endpoint, with no need to re-upload bytes or make the file public. See [Files API integration for image & video requests](/developers/model-capabilities/imagine/files/inputs). **Persist image & video outputs to Files** — set `storage_options` on any image or video request to save the generated asset to your Files storage; pair wit
You can manage your API keys via Management API at `https://management-api.x.ai`.
No matching records.