GPT-6.2 Sol
OpenAI — GPT-6.2 Sol
Model Details
GPT-6.2 Sol is the next generation of GPT-6.1 Sol, a fast, versatile model for everyday work such as implementing features, writing technical content, and automating recurring workflows across business applications.
-
Model launch date: November 17, 2026
-
Model lifecycle policy: OpenAI model deprecation notice periods
. This model follows OpenAI first-party lifecycle terms, with at least 6 months of deprecation notice for generally available models, unless safety or compliance concerns require a faster timeline. -
Model EOL date: Not announced.
-
End User License Agreements and Terms of Use: OpenAI models on Amazon Bedrock terms
-
Model lifecycle: Active
-
Context window: 1,050,000 tokens
-
Max output tokens: 128,000 tokens
| Input Modalities | Output Modalities |
|---|---|
Endpoints and APIs supported
The following tables show which endpoints and APIs GPT-6.2 Sol supports. For more information, see APIs supported by Amazon Bedrock and Inference endpoints supported by Amazon Bedrock.
Endpoint support
| Endpoint | Supported |
|---|---|
bedrock-runtime | |
bedrock-mantle |
APIs supported on bedrock-runtime
| Messages | Responses | Chat Completions | Converse | Invoke |
|---|---|---|---|---|
|
|
|
|
|
|
APIs supported on bedrock-mantle
| Messages | Responses | Chat Completions | Converse | Invoke |
|---|---|---|---|---|
|
|
|
|
|
|
On bedrock-mantle, both APIs use the /openai/v1 base path, not /v1. Use either API with this model:
For Responses, use
/openai/v1/responses.For Chat Completions, use
/openai/v1/chat/completions.
Capabilities and Features
Bedrock Features
Features supported using bedrock-runtime
| Supported | Not Supported |
|---|---|
|
Features supported using bedrock-mantle
| Supported | Not Supported |
|---|---|
|
Prompt caching
GPT-6.2 Sol supports both Implicit Prompt Caching and Explicit Prompt Caching. API support differs by endpoint:
Responses and Chat Completions support both caching types on the
bedrock-runtimeandbedrock-mantleendpoints.InvokeModel supports both caching types on the
bedrock-runtimeendpoint.Converse supports implicit caching on the
bedrock-runtimeendpoint. The nativecachePointfield isn't supported for explicit caching with this model.
For explicit caching, set prompt_cache_options.mode to explicit. Set prompt_cache_options.ttl to 30m, the only supported TTL and the default. In Responses requests, add "prompt_cache_breakpoint": {"mode": "explicit"} to an input_text content block. In Chat Completions and InvokeModel requests, add it to a text content part.
A cacheable prompt prefix must contain at least 1,024 tokens. You can include multiple explicit breakpoints, and each request can create up to four cache writes. Check the cache usage fields in the response to determine whether tokens were written to or read from the cache.
JSON Schema output
Use JSON Schema to set the format of the model response for streaming and non-streaming requests. Chat Completions and Responses support JSON Schema output on both the bedrock-runtime and bedrock-mantle endpoints. InvokeModel, InvokeModelWithResponseStream, Converse, and ConverseStream support JSON Schema output on the bedrock-runtime endpoint. Choose a model ID or inference profile ID from Programmatic access.
For Chat Completions, set
response_format.typetojson_schema. Putname,schema, andstrict: trueinresponse_format.json_schema.For Responses, set
text.format.typetojson_schema. Putname,schema, andstrict: trueintext.format.For InvokeModel and InvokeModelWithResponseStream, use the same
response_formatfields as Chat Completions.For Converse and ConverseStream, set
outputConfig.textFormat.typetojson_schema. InoutputConfig.textFormat.structure.jsonSchema, setnameandschema. Encode the schema as a JSON string. Then setadditionalModelRequestFields.text.format.stricttotrue.
Use an object schema. Put all fields in required. Set additionalProperties to false. Validate your schema before you send it. Check for refusals or incomplete responses before you parse the output.
For JSON Schema output with Converse and ConverseStream, you must set additionalModelRequestFields.text.format.strict to true, in addition to specifying the schema in outputConfig. Include the following field in your request.
{ "additionalModelRequestFields": { "text": { "format": { "strict": true } } } }
Converse content blocks
On the bedrock-runtime endpoint, Converse accepts text and
image content blocks in user messages. This model doesn't accept
document content blocks, and it doesn't accept an image content block
inside a toolResult. A request that includes either is rejected with a
ValidationException. To send a document to this model, use the Responses API with
an input_file content part instead.
Pricing
All prices are in USD per 1 million tokens for the Standard tier.
The Input — 30-minute cache write column is the price per 1 million tokens written to the prompt cache. The 30-minute figure is how long a cached prompt prefix is retained, not a quantity of tokens. For more information, see prompt caching.
Commercial In-Region prices include a 10% fee over OpenAI rates. You do not need to add this fee.
Long-context rates apply to the full request when input exceeds 272,000 tokens.
Priority and Flex tiers are not supported for this model.
Standard — Commercial Regions, short context (272K input tokens or fewer)
| Inference option | Input | Input — 30-minute cache write | Input — cache read | Output |
|---|---|---|---|---|
| In-Region | $2.20 | $2.75 | $0.11 | $11.00 |
| Geo CRIS | $2.20 | $2.75 | $0.11 | $11.00 |
| Global CRIS | $2.00 | $2.50 | $0.10 | $10.00 |
Standard — Commercial Regions, long context (more than 272K input tokens)
| Inference option | Input | Input — 30-minute cache write | Input — cache read | Output |
|---|---|---|---|---|
| In-Region | $4.40 | $5.50 | $0.22 | $16.50 |
| Geo CRIS | $4.40 | $5.50 | $0.22 | $16.50 |
| Global CRIS | $4.00 | $5.00 | $0.20 | $15.00 |
Programmatic Access
To call this model from code, use the following model IDs and endpoint URLs. For more information, see APIs supported by Amazon Bedrock and Inference endpoints supported by Amazon Bedrock.
| Endpoint | Model ID | In-Region endpoint URL | Geo inference ID | Global inference ID |
|---|---|---|---|---|
bedrock-mantle | openai.gpt-6.2-sol | https://bedrock-mantle.{region}.api.aws/openai/v1 | Not supported | Not supported |
bedrock-runtime | openai.gpt-6.2-sol | Not supported | us.openai.gpt-6.2-sol | global.openai.gpt-6.2-sol |
For in-Region access, use bedrock-mantle in us-east-1 (N. Virginia). On bedrock-runtime, the OpenAI-compatible base URL is https://bedrock-runtime.{region}.amazonaws.com/openai/v1. Use us.openai.gpt-6.2-sol for US geographic cross-Region inference or global.openai.gpt-6.2-sol for global cross-Region inference. Direct in-Region invocation is not supported on bedrock-runtime. Use a source Region enabled for the profile you choose; see Route model inference requests across AWS Regions with cross-Region inference.
Service Tiers
Amazon Bedrock offers several service tiers for different workloads. Standard gives you pay-per-token access with no commitment. To use it, set "service_tier": "default" or omit the field. 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-east-1 (N. Virginia) | |||
us-east-2 (Ohio) | |||
us-west-2 (Oregon) | |||
us-gov-west-1 (GovCloud West) | |||
us-gov-east-1 (GovCloud East) |
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) | |||
mx-central-1 | |||
me-south-1 (Bahrain) | |||
af-south-1 (Cape Town) | |||
sa-east-1 (São Paulo) |
Geo inference details
The destination Regions available to a geographic inference profile depend on the source Region. To retrieve the current routing configuration, call GetInferenceProfile from the source Region.
Geo: US
Geo inference ID: us.openai.gpt-6.2-sol
| Source Region | Destination Regions |
|---|---|
| us-east-1 (N. Virginia) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
| us-east-2 (Ohio) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
| us-west-1 (N. California) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-1 (N. California), us-west-2 (Oregon) |
| us-west-2 (Oregon) | us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
| ca-central-1 (Canada) | ca-central-1 (Canada), us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
| ca-west-1 (Calgary) | ca-west-1 (Calgary), us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon) |
Quotas and Limits
Quotas vary by account and Region. See Quotas for Amazon Bedrock and the model's service quota settings.
The output-token burndown rate is 10: each output token consumes 10 tokens of quota.
Sample Code
Step 1 - AWS Account: If you already have an AWS account, 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: You must have Python installed to use this guide. Then install the OpenAI SDK.
python3 -m pip install openai
Step 4 - Set environment variables
Set up your environment to use the API key for authentication.
On bedrock-runtime, set the model to us.openai.gpt-6.2-sol for US CRIS or global.openai.gpt-6.2-sol for Global CRIS. Direct in-Region invocation is not supported on this endpoint.
Step 5 - Run your first inference request
Save the file as bedrock-first-request.py.
bedrock-mantle
Use the settings from Step 4 - Set environment variables. Choose the bedrock-mantle tab. The Chat tab uses the Chat Completions API.
bedrock-runtime: OpenAI SDK
Use the settings from Step 4 - Set environment variables. Choose the bedrock-runtime tab. Send your request with the Responses API. The example uses the US CRIS profile. For Global CRIS, replace us.openai.gpt-6.2-sol with global.openai.gpt-6.2-sol.