Repository navigation
feat(model): add MiniMax provider support - #631
octo-patch wants to merge 8 commits into
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
|
Corrected the MiniMax-M3 per-token pricing in the provider config to match the published rates (input $0.6/M, output $2.4/M, cache read $0.12/M) and updated the corresponding test assertion. Ran the MiniMax provider tests (6 passed) and ruff on the changed Python files. |
|
Updated the MiniMax model availability probe to support both regional OpenAI-compatible and Anthropic-compatible endpoints, with matching request/response handling, and pushed commit fbd2c77. I ran the focused MiniMax tests (10 passed), the full Python suite (411 passed), Ruff, and the frontend lint, typecheck, and build. |
|
Thanks. I aligned the MiniMax provider config to the target pricing fields and pushed a new commit. I ran YAML assertions for the MiniMax provider config and |
…ut-pr631 # Conflicts: # python/valuecell/adapters/models/factory.py # python/valuecell/adapters/models/tests/test_minimax_provider.py
|
Updated the MiniMax provider metadata to include all supported Flash input modalities and current M3 pricing. I also adjusted the Anthropic boundary test setup so the provider's regional base URL remains under test. I ran the 12 MiniMax provider tests, Ruff, and git diff --check. |
Reason: Make MiniMax M3.1 Flash the first and default ordinary text model while preserving explicit M3, M2.7, saved/custom/legacy selections, and existing multimodal inputs.
Type of Change
New Feature
Description
MiniMax-M3.1-Flashthe provider default and first ordinary catalog choice; keeps MiniMax M3 as the second ordinary choice and hides legacy M2.7 from the ordinary catalog.reasoning_effort: maxthrough the OpenAI-compatible boundary andoutput_config.effort: maxthrough the Anthropic-compatible boundary.Testing
python3 -m py_compile python/valuecell/adapters/models/factory.py python/valuecell/adapters/models/tests/test_minimax_provider.pygit diff --checkChecklist