feat: add MiniMax provider registry support#98
Open
octo-patch wants to merge 1 commit into
Open
Conversation
octo-patch
force-pushed
the
octo/20260708-add-target-provider-model-to-existing-provider-registry-recvoNoSYsJNk9
branch
from
July 15, 2026 14:24
ee16ead to
7ef9dd5
Compare
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
1 participant
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.
Reason: add target provider/model to existing provider registry
Adds MiniMax M3 and MiniMax M2.7 to the embedded registry with model metadata, global and China endpoints, and completions-compatible and messages-compatible adapters. Keeps the messages-compatible base URL unchanged so the SDK appends /v1/messages.
Checks: