View a markdown version of this page

APIs supported by Amazon Bedrock - Amazon Bedrock

APIs supported by Amazon Bedrock

Inference APIs supported

Amazon Bedrock provides five main API patterns to perform inference. For new applications, we recommend the bedrock-runtime endpoint. The APIs are grouped by the service endpoint they use.

bedrock-runtime endpoint (recommended)

The bedrock-runtime.{region}.amazonaws.com endpoint supports the following APIs:

API method Use-case best suited for Key feature
Converse Multi-turn chat / standardizing The Converse API provides a unified interface for interacting with all models in Amazon Bedrock.
Invoke Single transactions / Large payloads The Invoke API provides direct access to models with more control over the request and response format.
Responses OpenAI-compatible, stateful conversations Use the Responses API for OpenAI-compatible stateful, multi-turn conversations — same OpenAI shape, plus Amazon Bedrock features such as Guardrails and cross-Region inference. On bedrock-runtime, requests are always synchronous and server-side tools are not available — see Endpoints supported by Amazon Bedrock for the full comparison.
Chat Completions OpenAI-compatible, stateless multi-turn chat Use the Chat Completions API for OpenAI-compatible stateless chat interactions.
Messages API Anthropic-native interface Use the Messages API through InvokeModel for direct access to Anthropic models using the native request format.

bedrock-mantle endpoint

The bedrock-mantle.{region}.amazonaws.com endpoint supports the following APIs:

API method Use-case best suited for Key feature
Responses API Stateful conversations with server-side tools Use the Responses API on bedrock-mantle for agentic applications that require built-in server-side tool use (search, code interpreter), multimodal inputs, and asynchronous inference.
Messages API Anthropic-native interface Use the Messages API for direct access to Anthropic models using the Anthropic-native request and response format.
Chat Completions Stateless multi-turn chat Use the Chat Completions API for lightweight, stateless, text-focused tasks where you need full control over chat history management and lower latency.

Read more about the APIs supported by Amazon Bedrock.

Deciding between APIs

The API you use depends on your use-case.

Use Case Recommended API
Migrating from OpenAI API-compatible endpoint Use the OpenAI-compatible Responses API or Chat Completions API on the bedrock-runtime endpoint — same OpenAI shape, plus Amazon Bedrock features such as Guardrails and cross-Region inference. According to OpenAI, the recommended API long-term is the Responses API.
Using models not compatible with OpenAI-compatible endpoint Use native Amazon Bedrock APIs: Converse and Invoke. For more information, see Inference using Invoke API.
Consistent interface across all models Converse API - Works with all models that support messages. Write code once and use it with different models. For example code, see Converse API examples.
Direct model access with full control Invoke API - Provides direct access to models with more control over request and response format. Use for generating text, images, and embeddings. For example code, see Invoke model code examples.
New to Amazon Bedrock We recommend using the bedrock-runtime endpoint with the Messages API, Chat Completions API, or Responses API for an OpenAI- or Anthropic-compatible interface.

Models supported by each API and endpoint

First, browse our models to decide on the model you want to use. Once you decide on the model you want to use, you can see the APIs it supports and choose an endpoint. We recommend the bedrock-runtime endpoint, which supports the Invoke, Converse, Responses, Chat Completions, and Messages APIs. The bedrock-mantle endpoint is also fully supported and offers the Responses, Chat Completions, and Messages APIs. Because the Responses, Chat Completions, and Messages APIs are available on both endpoints but do not have identical feature support on each, see Endpoints supported by Amazon Bedrock before you choose.