Repository navigation
docs(bedrock): document the native Responses API route for OpenAI models - #1699
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 7f5db62. Configure here.
mateo-berri
deleted the
litellm_docs_bedrock_runtime_native_responses
branch
September 24, 2026 21:33
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TLDR
Adds a section to the Bedrock provider page for the native Responses API route that BerriAI/litellm#42767 shipped on 2026-09-23. Until now bedrock.md described OpenAI models on Bedrock only through the Converse bridge, so a reader had no way to learn that
/v1/responsesonbedrock/us.openai.*andbedrock/global.openai.*now goes straight tohttps://bedrock-runtime.{region}.amazonaws.com/openai/v1/responses, that the opt-in is the cost map'ssupported_endpoints: ["/v1/responses"], which models carry it today, or how the route differs from the bridge (prompt_cache_keyworks,backgroundandweb_searchare dropped with a warning, remote image URLs are inlined)Changes
One new
## OpenAI models on the native Responses APIsection indocs/providers/bedrock.md, placed after the OpenAI GPT OSS section and before TwelveLabs Pegasus, with an SDK and a proxy tab. Every claim in it comes from the merged PR's description and fromlitellm/llms/bedrock/responses/transformation.pyon main. Nothing else on the page changes, so this does not overlap the pending chat-completions docs PR #1583, which waits on BerriAI/litellm#40775Note
Low Risk
Documentation-only change to the Bedrock provider page; no runtime or configuration behavior is modified in this PR.
Overview
Adds OpenAI models on the native Responses API to
docs/providers/bedrock.md, between the GPT OSS section and TwelveLabs Pegasus.The new section explains that opt-in models (
supported_endpoints: ["/v1/responses"]in the cost map, overridable viamodel_info/register_model) send/v1/responsesdirectly to Bedrock’sopenai/v1/responsesendpoint instead of the Converse chat-completions bridge—so parameters likeprompt_cache_keywork and cached tokens show in usage. It lists whichus./global.profiles use the native route vs bridge-only models (e.g. GPT-OSS), notes unchanged auth/region/cost behavior and customaws_bedrock_runtime_endpointhandling, and documents route-specific behavior (background/web_searchdropped with warnings, remote images inlined,file_searchemulated). SDK and proxy tabs include examples usinglitellm.responsesandcurlto/v1/responses.Reviewed by Cursor Bugbot for commit 7f5db62. Bugbot is set up for automated code reviews on this repo. Configure here.