xAI · Grok

Who can use it: Available to API teams using Chat Completions and Responses API; unavailable for multi-agent models and some deferred requests.

How to use it: Add the `guidelines` array to the request body; for each item, send the `type: "policy"`, relevant `category`, and `behavior: "decline"` fields.

Tip: Send only the categories you want to change; unspecified categories retain their default behavior.

Who can use it: For accounts using Grok Bot; the relevant desktop app version must be 0.75.2 or later.

How to use it: Open and approve the Auto-review rule suggestion shown on an approval card; rules can also be edited in Grok Bot settings.

Tip: Add rules for repeated, low-risk actions, but keep irreversible actions such as sending money or external messages subject to manual approval.

Who can use it: For Grok Bot users; Vault and bot email features are available in version 0.75.2 or later.

How to use it: Open Vault from Settings; ask a Bot to fill out a login or payment form, or forward an email from its own inbox.

Tip: Save only the information in Vault that automation actually needs, and keep Auto-review approval enabled for payment submissions.

Who can use it: For users with Grok Bot access; sharing permissions are subject to team administrator policies.

How to use it: In a Bot conversation, ask it to create a Page in report or dashboard format, or a video from a description or image; use the sharing menu for Pages.

Tip: For a report that needs ongoing updates, use a Page as a living workspace rather than a one-off file.

Who can use it: For Grok Bot users; each connector’s own account, region, and permission requirements apply.

How to use it: Connect Zoho CRM, GitHub, Gmail, or Google Calendar from Connect Apps; ask the Bot to perform the relevant action in a chat.

Tip: Select the correct regional data center for your account before signing in to Zoho CRM; choosing the wrong region may cause connection issues.

Who can use it: Open to applications from enterprise customers and companies building solutions around Grok; partnership access is subject to application and evaluation.

How to use it: Review and apply to the Transformation Partners or Marketplace Partners program at x.ai/partners.

Tip: If you’re planning an enterprise rollout, clarify upfront whether you fall under product integration or consulting/implementation services.

Who can use it: Announced as a sample workflow for Grok Bot users; production use depends on the relevant support system and permission connections.

How to use it: Connect the support queue and status page, then define periodic monitoring for IncidentWatch and scope, exclusions, and approval steps for IncidentSweep.

Tip: Have a person approve sample tickets, excluded records, and the exact response text before IncidentSweep sends anything.

Who can use it: Affects API customers using the older versioned slug; new applications should use 3.0 or `latest`.

How to use it: Change the `model` field in requests to `grok-voice-3.0` or `grok-voice-latest`.

Tip: If you use a versioned model in production, validate the migration in a test environment; `latest` makes automatic upgrades easier but does not provide version pinning.

Who can use it: Available to Speech to Speech API users; priced at 0,08 US dollars per minute, and `grok-voice-latest` routes to this model automatically.

How to use it: Use `model=grok-voice-3.0` or `model=grok-voice-latest` in a WebSocket Speech to Speech connection; existing API parameters remain unchanged.

Tip: Start with `grok-voice-latest` for low-latency customer service scenarios; pin the versioned slug if you don’t want version changes.

Who can use it: Mac and Windows users with Grok Bot access; the 200 MB total message limit and plan limits still apply separately.

How to use it: Attach files to a Bot chat as usual; skills are selected automatically from installed plugins.

Tip: Before sending large videos, check the 1 GB limit and the requirement that the Bot be able to view the video.

Who can use it: Available immediately to new customers; being rolled out gradually to existing SuperGrok, Cursor, and X Premium subscribers, with global availability targeted for the days following the announcement.

How to use it: Compare plans at x.ai/pricing; existing subscribers can see the option to switch and, if applicable, a prorated refund offer under Billing settings.

Tip: If you use Grok and Cursor heavily together, check the shared usage pool and note that third-party model usage is billed separately.

Who can use it: For Grok Bot users; some email and connector capabilities depend on plan or administrator policies.

How to use it: Request an email address or ask for an X search from within Grok Bot; enable app cards through Connect Apps.

Tip: Use date, like, and repost filters in X search to narrow large result sets.

Who can use it: Users with Grok Bot access; payment and finance connectors are subject to account, region, and approval policies.

How to use it: Connect QuickBooks Online from Connect Apps; during payment, select X Money or Stripe Link from the approval card.

Tip: In payment flows, use Auto-review to require approval for every purchase and money transfer step.

Who can use it: Grok Bot users; Google Slides delivery depends on the permissions of the connected Google account.

How to use it: Ask a Bot to prepare a presentation, choose the example-slide approach, and get the final output as PowerPoint or Google Slides.

Tip: Before generating a presentation, specify the target audience, slide count, and brand template clearly; keep final sharing subject to human approval.

Who can use it: For Microsoft Foundry users in Global Standard and US Data Zone Standard deployments; short-context pricing starts at 2 US dollars for input and 6 US dollars for output per 1 million tokens.

How to use it: Select and deploy the `grok-4.7` model in the Foundry Models catalog; call it in your application using Foundry APIs and Microsoft Entra ID or an API key.

Tip: Teams with US Data Zone requirements should also test long-context and regional pricing differences when choosing a deployment region.

Who can use it: In Grok Bot’s Language options, for supported accounts and client versions.

How to use it: Select Marathi, Tamil, Telugu, Swahili, or Hausa from Settings → Language.

Tip: If you use Follow System to match the system language, make sure your computer’s language is one of the supported options.

Who can use it: Expert mode is available on grok.com; Fast mode is available to paid subscribers.

How to use it: In a grok.com chat, select Expert or, if you’re on a paid plan, Fast from the model/mode selector.

Tip: Try Expert for lengthy coding and research tasks, and Fast for short, time-sensitive questions.

Who can use it: SuperGrok Plus and SuperGrok Heavy subscribers.

How to use it: Sign in to grok.com; open an existing Bot or chat thread from the Bots section of the sidebar.

Tip: Enable browser notifications so you don’t miss a Bot’s completed tasks while the tab is in the background.

Who can use it: Affects API customers using the old 1.0 slug; routing is applied automatically at the same price.

How to use it: Set `model` to `grok-voice-transcribe-2.0` in your client code, or use the existing default routing.

Tip: After automatic routing, compare the language, timestamps, and diarization output against your production samples again.

Who can use it: Grok Bot desktop and web users; the apps shown may vary based on account and team permissions.

How to use it: Open Connect Apps in Grok Bot, select an app by category or search, and complete the connection.

Tip: Before connecting a connector, check the card to see which account and permissions the Bot will use.

Who can use it: Users with access to Grok Bot; Primary Bot setup required.

How to use it: Use the starred Primary Bot during Grok Bot setup or in Bot details; approve the task from the suggested task card.

Tip: Start with low-risk, repetitive tasks for proactive suggestions; require approval for external communications and financial decisions.

Who can use it: Team Bot owners and authorized managers on Teams and Enterprise plans.

How to use it: Add a teammate from the Managers section in Team Bot details; choose a shape and color in the avatar editor.

Tip: Grant the manager role only to people who will oversee the Bot’s permissions and connector scope.

Who can use it: Teams and Enterprise plans using Team Bots; automatic updates are available in the desktop app.

How to use it: Use the voice call button in a Team Bot chat; you can turn off automatic updates in Settings → Updates.

Tip: If update timing is critical on corporate computers, align the Automatic Updates setting with your IT policy.

Who can use it: Teams using Team Bots and a Slack connection; admin approval and channel permissions are required.

How to use it: Add the Team Bot to a Slack channel; respond to the card when approval is required, or ask the Team Bot to send a message to another Bot.

Tip: Grant approval authority only to people who will assess the action; in public channels, prefer sending sensitive results to a private message.

Who can use it: Public beta on Teams and Enterprise plans.

How to use it: Configure a Grok Bot for your team, add the required plugins, credentials, files, and skills, then share it as a Team Bot.

Tip: Give the Team Bot only the files and permissions it needs for its role; test the sharing settings to confirm that personal conversations remain private.

Who can use it: Grok Imagine users; the plan’s video-generation allowance and rate limits apply.

How to use it: Select the Loop tile on the Imagine home page, or open an image’s Make Video menu and use Loop.

Tip: For scenes suited to looping, such as product rotations or location transitions, keep the start and end images in the same composition.

Who can use it: Grok Bot users; a connected Outlook account and sending permissions are required.

How to use it: Connect Outlook through Connect Apps, ask the Bot to prepare a draft, and use the Send email option on the chat card.

Tip: When using it for the first time, check the sender address, recipients, and signature on the draft card.

Who can use it: Available to developers using the API; the legacy `user` field continues to be accepted.

How to use it: Add an opaque value generated by your application for each end user to the `safety_identifier` field.

Tip: Do not put an email address or directly identifying personal data in the identifier field; use an irreversible, opaque application ID.

Who can use it: Available to Grok Bot users through Settings → Language.

How to use it: Select a language in Settings → Language, or turn on Follow System.

Tip: For shared team use, check the client language and the Bot’s response language separately.

Who can use it: For API teams on the global endpoint and US regional endpoint; the applicable long-context price applies to context of up to 500,000 tokens in the public API.

How to use it: Use `model: "grok-4.7"` in a Responses API request; set the `reasoning_effort` field to low, medium, high, or xhigh.

Tip: Reduce cost and latency in long agent loops by using `prompt_cache_key` and, when needed, Context Compaction.

Who can use it: Copilot Pro, Pro+, Max, Business, and Enterprise SKUs; phased rollout and Business/Enterprise admin policies apply.

How to use it: Select Grok 4.7 from the model picker in a supported Copilot client; a Business or Enterprise admin can manage access through the Copilot model policy.

Tip: Monitor your team’s quota, taking usage-based provider pricing and the model’s phased rollout into account.

Who can use it: SuperGrok Heavy subscribers.

How to use it: Open the Bots section in the grok.com sidebar; chat directly with a Bot or add multiple Bots to a group.

Tip: Connect the resources the Bot needs without leaving the chat, and enable browser notifications for long-running tasks.

Who can use it: Text Edit beta and Precise Edit are available on all plans; video keyframes are available on paid plans.

How to use it: Open an image in Imagine and select Text Edit or Precise Edit; on a paid plan, lock an image as an intermediate keyframe when editing a video.

Tip: For posters and social media images, use Text Edit to change text instead of regenerating it, preserving character and layout consistency.

Who can use it: Accounts with access to Grok Bot and the relevant Cloud Agent; plan and team policies apply.

How to use it: Ask the Bot in chat to start a Project and plan the work and distribute it to Cloud Agents.

Tip: Clearly specify the success criteria, file scope, and stopping conditions for the work sent to the Cloud Agent.

Who can use it: Speech-to-Text API users; batch is $0.10/hour, streaming is $0.20/hour.

How to use it: Use `grok-voice-transcribe-2.0` in the Speech-to-Text API; to stay on the older version, explicitly pin the `grok-voice-transcribe-1.0` slug.

Tip: Enable key terms and diarization options for phone calls and short multilingual commands, then send the output directly into your workflow.

Who can use it: Grok Build users; activates in new sessions.

How to use it: Start a new session to continue working with Grok Build; view notes with `/memory` and edit them with `/dream`.

Tip: Explicitly ask it to save project conventions and test commands to memory; don’t turn temporary task statuses into persistent notes.

Who can use it: Grok Bot users with a connected Google Drive, OneDrive, or Gmail account.

How to use it: Connect the relevant app through Connect Apps, then ask the Bot to upload the file or attach it to a Gmail draft.

Tip: Test corporate folder permissions and sharing scope with a low-sensitivity file first.

Who can use it: Grok Bot accounts that can use Routines.

How to use it: In the Routines section of Bot details, right-click the relevant routine and select Pause or Resume.

Tip: Pause a routine instead of deleting it during temporary maintenance periods; check connected connector sessions before enabling it again.

Who can use it: Grok Imagine users; video generation limits and plan entitlements apply.

How to use it: After adding an image in the Imagine creator, choose its role: First frame, Last frame, Loop, or Reference.

Tip: Try the starting/ending frame to control camera movement, or Reference mode for character consistency.

Who can use it: Accounts using the Grok Bot desktop app; team admins can restrict this with network controls.

How to use it: Turn on Route egress through this desktop in Settings → Computer.

Tip: Before enabling this setting, test local network permissions and verify that the Bot can’t run when the computer is off.

Who can use it: Grok Bot users; subject to the relevant repository and provider permissions.

How to use it: When the bot requests access, select a provider from the repository connection card, sign in, and allow the task to continue.

Tip: Grant the bot access only to the required repository and read/write scope rather than opening access to your entire organization.

Who can use it: Available on Grok Bot plans; optional usage and administrator limits are subject to plan policy.

How to use it: Go to Settings → Usage & Billing to monitor weekly usage and set a monthly on-demand limit.

Tip: Set a monthly limit before enabling automated routines, and monitor usage spikes from intensive workflows.

Who can use it: Grok Bot desktop users; Marketplace content may vary based on account and team access.

How to use it: Add an account from the Account menu, then select and add a plugin or Bot from Marketplace.

Tip: To avoid mixing personal and work accounts, check each account’s connector and Bot lists separately.

Who can use it: The draft feature is available to Grok Bot users; mandatory Auto-review is available to Enterprise administrators.

How to use it: Ask the bot to prepare an email or Slack message; an Enterprise administrator can enable Auto-review and team rules in the dashboard.

Tip: Keep draft mode on for all messages sent to external customers, and automate only trusted internal notifications.

Who can use it: Users with Grok Bot access; site and field support may vary by page.

How to use it: Fill out the chat form when the bot requests information; on Mac, right-click a text field and use AutoFill.

Tip: Use Secure Form or AutoFill fields instead of sharing passwords and payment codes in chat messages.

Who can use it: Grok web users; voice options and Imagine generation are subject to plan limits.

How to use it: Open a Project and select Imagine from the composer; for voice use, select Aurora or Liora from Voice Library.

Tip: When generating images from project context, keep files and instructions in the same Project to avoid repeatedly transferring context.

Who can use it: Grok web users; content visibility and team-sharing settings apply.

How to use it: Open Library from the Grok sidebar, then choose a view, sorting, and filters.

Tip: Separate long-term project files using tags and visibility filters to make them quicker to reuse.

Who can use it: Grok Bot users; Bot addition and Enterprise access restrictions depend on administrator settings.

How to use it: Open the Bots category or search in Marketplace, then select Add from a Bot page.

Tip: The Verified badge helps verify the source, but review the connector permissions requested by each Bot individually.

Who can use it: Grok and Cursor Enterprise customers; two weeks of free use from the announcement date, followed by enterprise plan terms.

How to use it: Enable Grok Bot in the admin dashboard and grant organization members access.

Tip: Configure access groups, network controls, and audit log policies before rolling it out widely.

Who can use it: In Grok Bot Language settings, on supported client versions.

How to use it: Select one of the supported languages under Settings → Language, or use Follow System.

Tip: When creating a new Bot for multilingual teams, check the default greeting language.

Who can use it: Grok Bot users; depends on task duration, plan, and computer resources.

How to use it: Give Bot a long task with a single goal and completion condition; let it run in the background.

Tip: Define interim outputs or checkpoints for long tasks; test fully open-ended tasks before making them routine.

Who can use it: API customers; migration will happen through automatic routing on November 2, 2026, but an explicit migration is recommended.

How to use it: Change the `model` field in your code to `grok-imagine-image-2.0` and explicitly manage quality with `low`, `medium`, or `auto`.

Tip: Instead of relying on automatic routing, update the model field in advance and test for quality and cost regressions.

Who can use it: On existing API and product surfaces that use Grok 4.6; the announcement does not specify a new access region or plan.

How to use it: No separate setting is required; the safety behavior is built into the deployment of the Grok 4.6 model.

Tip: Use model outputs in biology workflows alongside expert review and your organization’s biosafety procedures.

Who can use it: Grok Bot desktop app users.

How to use it: Open a pull request link in a Bot chat; create the new Bot from the section you want in the sidebar.

Tip: When requesting a code review, also verify the PR status and target branch; the preview shows only link metadata.