1. InvokeModel and Streaming Basics2. Converse API Patterns3. Five Ways to Call Bedrock: Converse, Invoke, Messages, Responses, Chat Completions
Five Ways to Call Bedrock: Converse, Invoke, Messages, Responses, Chat Completions
๐ Inference APIsโฑ 11 minโญ 75 XP
Bedrock Now Speaks Every Provider's Native API
Beyond Converse and InvokeModel, Amazon Bedrock exposes provider-native API surfaces so you can point existing SDKs at Bedrock with minimal rewrites:
Converse API โ AWS-native, model-agnostic, unified message schema across every supported provider.
InvokeModel / InvokeModelWithResponseStream โ Lowest-level access with per-provider request/response bodies.
Messages API โ Anthropic's native schema, callable via the standard anthropic SDK pointed at Bedrock.
Responses API โ OpenAI's native schema for models like openai.gpt-oss-120b, callable via the standard openai SDK.
Chat Completions API โ OpenAI-compatible schema for teams migrating existing Chat Completions integrations.
Key idea: Choose Converse for portability across model families, or a provider-native API when you want zero-friction reuse of an existing Anthropic/OpenAI SDK integration.
๐งช Knowledge Check
Press 1-4 to select1 of 2
Why would a team use the Messages or Responses API on Bedrock instead of Converse?
They perform better on all models
To reuse an existing Anthropic/OpenAI SDK integration with minimal code changes
Converse is deprecated
They are the only APIs with streaming
Five Ways to Call Bedrock: Converse, Invoke, Messages, Responses, Chat Completions Tutorial | Inference APIs โ AWS Bedrock Academy