Grok 4.6
xAI — Grok 4.6
Model Details
Grok 4.6 is xAI's frontier model built for coding, agentic tasks, and knowledge work. It builds on previous generations of Grok with a particular focus on long-running agents and more ambitious interactive work. It offers 500K context window and configurable reasoning efforts (low, medium, high, xhigh).
Model launch date: August 18, 2026
Model EOL date: N/A
End User License Agreements and Terms of Use: View
Model lifecycle: Active
Context window: 500K tokens
Reasoning: Supported (configurable: low, medium, high, xhigh)
| Input Modalities | Output Modalities | APIs supported | Endpoints supported |
|---|---|---|---|
Responses | bedrock-runtime | ||
Chat Completions | bedrock-mantle | ||
Converse | |||
Invoke | |||
Capabilities and Features
Bedrock Features
Features supported using bedrock-runtime endpoint
Features supported using bedrock-mantle endpoint
| Supported | Not Supported |
|---|---|
|
— |
Pricing
| Inference option | Input | Output | Cache read |
|---|---|---|---|
| In-Region | $2.20 | $6.60 | $0.55 |
| Geo CRIS | $2.20 | $6.60 | $0.55 |
| Global CRIS | $2.00 | $6.00 | $0.50 |
All prices are per 1 million tokens. Pricing shown is for the Standard tier.
Priority and Flex tier support: In addition to Standard, Grok 4.6 supports the Priority and Flex service tiers. Priority is billed at 2x the Standard per-token rate (a 100% premium) in exchange for prioritized processing and faster response times, while Flex is billed at 0.5x the Standard rate (a 50% discount) for flexible, non-time-sensitive workloads. Apply these multipliers to the Standard rates shown above to determine Priority and Flex pricing. For more information, see service tiers.
Programmatic Access
Use the following model IDs and endpoint URLs to access this model programmatically. For more information about the available APIs and endpoints, see APIs supported and Endpoints supported.
| Endpoint | Model ID | In-Region endpoint URL | Geo inference ID | Global inference ID |
|---|---|---|---|---|
bedrock-mantle |
xai.grok-4.6 |
https://bedrock-mantle.{region}.api.aws/openai/v1 |
Not supported | Not supported |
bedrock-runtime |
xai.grok-4.6 |
Not supported | us.xai.grok-4.6 |
global.xai.grok-4.6 |
For example, if region is us-west-2 (Oregon), then the bedrock-mantle endpoint URL will be "https://bedrock-mantle.us-west-2.api.aws/openai/v1". On bedrock-runtime, the base URL is "https://bedrock-runtime.{region}.amazonaws.com/openai/v1" and requests must name the geographic cross-Region inference ID us.xai.grok-4.6 or global.xai.grok-4.6 as the model.
Service Tiers
Amazon Bedrock offers multiple service tiers to match your workload requirements. Standard provides pay-per-token access with no commitment (set "service_tier": "default" or omit the field). Priority delivers faster, prioritized processing for a price premium (set "service_tier": "priority"). Flex provides lower-cost access for flexible, non-time-sensitive workloads (set "service_tier": "flex"). For more information, see service tiers.
| Standard | Priority | Flex | Reserved |
|---|---|---|---|
Regional Availability
Regional availability at a glance
Amazon Bedrock offers three inference options: In-Region keeps requests within a single Region for strict compliance, Geo Cross-Region routes across Regions within a geography (such as US, EU, and APAC) while respecting data residency, and Global Cross-Region routes anywhere worldwide when there are no residency constraints. Refer to the Regional availability by models page for more details.
Availability differs by endpoint.
Availability using the bedrock-mantle endpoint
| Region | In-Region | Geo | Global |
|---|---|---|---|
us-west-2 (Oregon) |
Availability using the bedrock-runtime endpoint
| Region | In-Region | Geo | Global |
|---|---|---|---|
us-east-1 (N. Virginia) | |||
us-east-2 (Ohio) | |||
us-west-1 (N. California) | |||
us-west-2 (Oregon) | |||
ca-central-1 (Canada) | |||
ca-west-1 (Calgary) | |||
eu-central-1 (Frankfurt) | |||
eu-central-2 (Zurich) | |||
eu-north-1 (Stockholm) | |||
eu-south-1 (Milan) | |||
eu-south-2 (Spain) | |||
eu-west-1 (Ireland) | |||
eu-west-2 (London) | |||
eu-west-3 (Paris) | |||
ap-east-2 (Taipei) | |||
ap-northeast-1 (Tokyo) | |||
ap-northeast-2 (Seoul) | |||
ap-northeast-3 (Osaka) | |||
ap-south-1 (Mumbai) | |||
ap-south-2 (Hyderabad) | |||
ap-southeast-1 (Singapore) | |||
ap-southeast-2 (Sydney) | |||
ap-southeast-3 (Jakarta) | |||
ap-southeast-4 (Melbourne) | |||
ap-southeast-5 (Malaysia) | |||
ap-southeast-6 (New Zealand) | |||
ap-southeast-7 (Thailand) | |||
il-central-1 (Tel Aviv) | |||
me-central-1 (UAE) | |||
me-south-1 (Bahrain) | |||
af-south-1 (Cape Town) | |||
sa-east-1 (São Paulo) |
Quotas and Limits
Your AWS account has default quotas to maintain the performance of the service and to ensure appropriate usage of Amazon Bedrock. The default quotas assigned to an account might be updated depending on regional factors, payment history, fraudulent usage, and/or approval of a quota increase request. For more information, see Quotas for Amazon Bedrock documentation and see the limits for the model.
Sample Code
Step 1 - AWS Account: If you have an AWS account already, skip this step. If you are new to AWS, sign up for an AWS account
Step 2 - API key: Go to the Amazon Bedrock console
Step 3 - Get the SDK: To use this getting started guide, you must have Python already installed. Then install the relevant software depending on the APIs you are using.
Step 4 - Set environment variables: Configure your environment to use the API key for authentication.
Note
On bedrock-runtime, name a cross-Region inference profile as the model — us.xai.grok-4.6 or global.xai.grok-4.6. This model is not available for in-Region inference on that endpoint. Your IAM identity also needs bedrock:InvokeModel on your account's default project (arn:aws:bedrock:{region}:{account-id}:project/default) in addition to the inference profile.
Step 5 - Run your first inference request: Save the file as bedrock-first-request.py
Usage Considerations and Limitations
Reasoning effort — Reasoning is always active by default. You can configure effort through the
reasoningparameter:"low"(default),"medium","high", or"xhigh". Reasoning content is encrypted and can be returned by passinginclude: ["reasoning.encrypted_content"]in the Responses API request. You can send the encrypted content back in subsequent turns to provide reasoning context for multi-turn conversations. The Chat Completions API does not return reasoning tokens.response = client.responses.create( model="us.xai.grok-4.6", reasoning={"effort": "high"}, include=["reasoning.encrypted_content"], input="Explain quantum entanglement simply." ) print(response.output_text)