Repository navigation
Conversation
…uting Add bedrock_mantle/xai.grok-4.3 to the model cost map with Responses API capability metadata and the openai/v1 wire path, so ProviderConfigManager routes through BedrockMantleResponsesAPIConfig (SigV4-capable) instead of falling back to the bearer-only chat bridge. Fixes BerriAI#31196
Contributor
|
Too many files changed for review. ( |
|
|
6 tasks done
Contributor
|
Superseded by rolling registry audit #37902, which reverified and absorbed the provider-documented metadata changes at field level |
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.
Summary
Register
bedrock_mantle/xai.grok-4.3in the model cost map so Bedrock Mantle routes Responses API calls throughBedrockMantleResponsesAPIConfig(SigV4-capable) instead of falling back to the bearer-only chat bridge.Fixes #31196
Motivation
xai.grok-4.3on Amazon Bedrock Mantle supports the native Responses API on the/openai/v1path with SigV4/IAM auth, but LiteLLM had nomodel_costentry for this model. As a result,mantle_supports_responses()returnedFalse,get_provider_responses_api_config()returnedNone, and requests were forced onto the chat-completions bridge that only supports bearer tokens.Changes
bedrock_mantle/xai.grok-4.3tomodel_prices_and_context_window.jsonand the backup JSON with:use_openai_responses_path: true(AWS/openai/v1wire path)supported_endpoints: ["/v1/chat/completions", "/v1/responses"]mantle_supports_responsesTests
Result: 3 passed
Notes
model_cost.bedrock_mantle/*entries today).