Published: 20 August 2026
Grok 4.6 became generally available on Amazon Bedrock on 19 August 2026, priced at $2 per million input tokens and $6 per million output, in every AWS Region where Bedrock is offered. The model keeps its 500K-token context window and its four reasoning effort levels.
What changed for Grok 4.6 on Amazon Bedrock
AWS added xAI’s flagship with two cross-Region inference profiles.
- The US Geo profile, us.xai.grok-4.6, routes requests only within United States geography for teams with data-residency obligations.
- The global profile, global.xai.grok-4.6, serves from any commercial Region where the model is available, which AWS positions as the higher-throughput and lower-cost option during demand spikes.
The model runs on the bedrock-runtime endpoint and supports the Responses, Chat Completions and Converse APIs, so existing Bedrock call sites do not need rewriting. Standard account controls apply: model invocation logging to Amazon S3 or CloudWatch Logs, CloudWatch metrics, and cost itemisation in AWS Cost Explorer and the Cost and Usage Report.
Grok 4.6 pricing, context window and reasoning settings
Pricing on Bedrock is $2 per million input tokens and $6 per million output, the same rates xAI published at the model’s launch. The context window stays at 500K tokens, and the four configurable reasoning effort levels, low, medium, high and xhigh, carry over unchanged from xAI’s own API.
Grok 4.6 itself is not new. xAI released it on 12 August 2026 as a post-training upgrade aimed at long-running agents, coding and knowledge work, and it was already reachable through the xAI API, OpenRouter, Cursor, Vercel and Cloudflare. What is new is the AWS route.
How this compares to calling the xAI API directly
The token price is identical, so this is not a cost decision. What changes is the surrounding plumbing: IAM instead of a separate API key, invocation logs in your own account, and spend that lands in the same AWS reports finance already reviews rather than a second vendor invoice.
The one capability the xAI API cannot offer is the US Geo profile. For an organisation whose policy forbids sending prompts to a third-party endpoint, that profile is the difference between using Grok 4.6 and not using it at all.
What this means
This matters to exactly one group: regulated teams already standardised on Bedrock who wanted Grok 4.6 and could not clear the procurement or residency hurdle. For them it removes a real blocker, and cross-Region inference makes capacity planning someone else’s problem. Testing it against Claude Opus 5 and Gemini 3.7 Flash on Bedrock is a reasonable next step.
For everyone else, this is a distribution announcement rather than a model release, and it changes nothing about what Grok 4.6 can do. If you already call the xAI API or route through OpenRouter, there is no reason to migrate. Read it as a signal about where enterprise model buying is settling, not as news about capability.
For more information visit the official AWS announcement on Grok 4.6.
