# GPT-5.5
##  OpenAI — GPT-5.5
## Model Details
GPT-5.5 is OpenAI's most capable model, designed for advanced coding, research, analysis, software operation, document workflows, and long-running agentic tasks. GPT-5.5 can understand open-ended goals, use tools, reason across longer workflows, navigate ambiguity, and carry complex tasks through to completion with less orchestration. For more information about model development and performance, see the [model/service card](https://deploymentsafety.openai.com/gpt-5-5/gpt-5-5.pdf).
+ **Model launch date:** June 1, 2026
+ **EOL no sooner than:** June 1, 2027
+ **Legacy period:** at least 6 months
+ **Model lifecycle policy:** [Model lifecycle (For Models Launched Prior to Sept 7 2026)](model-lifecycle-legacy.md)
+ **Model EOL date:** N/A
+ **End User License Agreements and Terms of Use:** [View](https://aws.amazon.com/legal/bedrock/third-party-models/)
+ **Model lifecycle:** Active
+ **Context window:** 1,050,000 tokens, shared between input and output
+ **Max output tokens:** 128,000
+ **Marketplace product ID:** `prod-indw4nwkcsyua`
| **Input Modalities** | **Output Modalities** |
| --- | --- |
|  Audio |  Embedding |
|  Image |  Image |
|  Speech |  Speech |
|  Text |  Text |
|  Video |  Video |
## Endpoints and APIs supported
The following tables show which endpoints and APIs are supported for GPT-5.5. For more information, see [APIs supported by Amazon Bedrock](apis.md) and [Inference endpoints supported by Amazon Bedrock](endpoints.md).
**Endpoint support**
| **Endpoint** | **Supported** |
| --- | --- |
| bedrock-runtime |  |
| bedrock-mantle |  |
**APIs supported on `bedrock-runtime` endpoint**
| **Messages** | **Responses** | **Chat Completions** | **Converse** | **Invoke** |
| --- | --- | --- | --- | --- |
|  |  |  |  |  |
**APIs supported on `bedrock-mantle` endpoint**
| **Messages** | **Responses** | **Chat Completions** | **Converse** | **Invoke** |
| --- | --- | --- | --- | --- |
|  |  |  |  |  |
**Note**
On `bedrock-mantle`, both inference 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`.
This applies to inference only. Model discovery stays on `/v1/models`, as it does for every model on `bedrock-mantle`. A request to `/openai/v1/models` returns `404`. For more information, see [Get list of models](models-get-info.md).
**Tip**
Whenever possible, we recommend using the `bedrock-runtime` endpoint for new applications. See [Inference endpoints supported by Amazon Bedrock](endpoints.md) for details.
## Capabilities and Features
***Bedrock Features***
**Features supported using `bedrock-runtime` endpoint**
| **Supported** | **Not Supported** |
| --- | --- |
| +  [Projects (default project only)](projects.html)
+  [Invocation logs](model-invocation-logging.html)
+  [Response streaming](/bedrock/latest/APIReference/API_runtime_InvokeModelWithResponseStream.html)
+  [Abuse detection](abuse-detection.html)
+  [Guardrails](guardrails.html) ([Converse API](conversation-inference.html) only)
+  [Application inference profiles](cost-mgmt-application-inference-profiles.html) ([Converse API](conversation-inference.html) only; not supported with Responses or Chat Completions APIs)
+  [Implicit Prompt Caching](prompt-caching.html#prompt-caching-implicit) (Responses API only; automatic, no request parameters)
+  [Structured outputs](structured-output.html) (JSON Schema; Responses API)
+  [Reasoning Summaries](https://developers.openai.com/api/docs/guides/reasoning#reasoning-summaries) (Responses, [Converse](conversation-inference.html), and ConverseStream APIs; on Converse, set `additionalModelRequestFields.reasoning.summary`) | +  [Explicit Prompt Caching](prompt-caching.html#prompt-caching-explicit)
+  [Server-side tool use](tool-use.html)
+  [Intelligent prompt routing](prompt-routing.html)
+  [Count tokens](count-tokens.html)
+  [Watermarking](watermarking.html) |
**Features supported using `bedrock-mantle` endpoint**
| **Supported** | **Not Supported** |
| --- | --- |
| +  [Server-side tool calling](tool-use.html)
+  [Projects](projects.html)
+  [Client-side tool calling](tool-use.html)
+  [Reasoning Summaries](https://developers.openai.com/api/docs/guides/reasoning#reasoning-summaries) (Responses API only) | +  [Watermarking](watermarking.html) |
**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](prompt-caching.md).
Commercial In-Region prices include a 10% fee over OpenAI rates. You do not need to add this fee.
Long-context rates apply to all input and output tokens, not just tokens above 272K.
*Priority and Flex tiers are not supported for this model.*
### Commercial Regions — short context (272K input tokens or fewer)
| **Inference option** | **Input** | **Input — 30-minute cache write** | **Input — cache read** | **Output** |
| --- | --- | --- | --- | --- |
| In-Region | $5.50 | — | $0.55 | $33.00 |
### Commercial Regions — long context (more than 272K input tokens)
| **Inference option** | **Input** | **Input — 30-minute cache write** | **Input — cache read** | **Output** |
| --- | --- | --- | --- | --- |
| In-Region | $11.00 | — | $1.10 | $49.50 |
## 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](apis.html) and [Endpoints supported](endpoints.html).
| **Endpoint** | **Model ID** | **In-Region endpoint URL** | **Geo inference ID** | **Global inference ID** |
| --- | --- | --- | --- | --- |
| bedrock-runtime | openai.gpt-5.5 | Not supported | us.openai.gpt-5.5 | global.openai.gpt-5.5 |
| bedrock-mantle | openai.gpt-5.5 | https://bedrock-mantle.{region}.api.aws/openai/v1 | Not supported | Not supported |
*For example, if region is us-east-1 (N. Virginia), then the bedrock-mantle endpoint URL will be "https://bedrock-mantle.us-east-1.api.aws/openai/v1". On `bedrock-runtime`, the base URL is "https://bedrock-runtime.{region}.amazonaws.com/openai/v1" and requests must name a cross-Region inference ID — `us.openai.gpt-5.5` or `global.openai.gpt-5.5` — 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 the fastest response times for a price premium (set `"service_tier": "priority"`). **Flex** provides lower-cost access for flexible, non-time-sensitive workloads (set `"service_tier": "flex"`). **Reserved** provides dedicated throughput with a term commitment for predictable workloads; it is set at the account level rather than per request (contact your AWS account team to enable). For more information, see [service tiers](service-tiers-inference.html).
| **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](models-region-compatibility.md) 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) |  |  |  |
**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) |  |  |  |
| mx-central-1 (Mexico) |  |  |  |
| 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](quotas-increase.html). For more information, see [Quotas for Amazon Bedrock](quotas.md) documentation and see the [limits](/general/latest/gr/bedrock.html#limits_bedrock) 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](https://portal.aws.amazon.com/billing/signup).
**Step 2 - API key:** Go to the [Amazon Bedrock console](https://console.aws.amazon.com/bedrock/home#/api-keys/long-term/create) and generate a long-term API key.
**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.
For both APIs, choose the OpenAI SDK tab.
------
#### [ OpenAI SDK ]
```
pip install openai
```
------
### Step 4 - Set environment variables
Configure your environment to use the API key for authentication.
------
#### [ bedrock-runtime ]
```
OPENAI_API_KEY=""
OPENAI_BASE_URL="https://bedrock-runtime.us-east-2.amazonaws.com/openai/v1"
```
------
#### [ bedrock-mantle ]
```
OPENAI_API_KEY=""
OPENAI_BASE_URL="https://bedrock-mantle.us-east-2.api.aws/openai/v1"
```
------
**Note**
On `bedrock-runtime`, name a cross-Region inference profile as the model — `us.openai.gpt-5.5` or `global.openai.gpt-5.5`. 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`
#### bedrock-mantle
Use the settings from [Step 4 - Set environment variables](#model-card-openai-gpt-55-sample-code-environment). Choose the `bedrock-mantle` tab. The Chat tab uses the Chat Completions API.
------
#### [ Responses API ]
```
from openai import OpenAI
client = OpenAI()
response = client.responses.create(
model="openai.gpt-5.5",
input="Can you explain the features of Amazon Bedrock?"
)
print(response)
```
------
#### [ Chat ]
```
from openai import OpenAI
client = OpenAI()
response = client.chat.completions.create(
model="openai.gpt-5.5",
messages=[{"role": "user", "content": "Can you explain the features of Amazon Bedrock?"}]
)
print(response)
```
------