Skip to content

feat: add MiniMax provider registry support - #98

Open
octo-patch wants to merge 2 commits into
m0n0x41d:devfrom
octo-patch:octo/20260708-add-target-provider-model-to-existing-provider-registry-recvoNoSYsJNk9
Open

feat: add MiniMax provider registry support#98
octo-patch wants to merge 2 commits into
m0n0x41d:devfrom
octo-patch:octo/20260708-add-target-provider-model-to-existing-provider-registry-recvoNoSYsJNk9

Conversation

@octo-patch

@octo-patch octo-patch commented Jul 15, 2026

Copy link
Copy Markdown

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:

  • go test -race ./internal/provider ./internal/config
  • go vet ./internal/provider ./internal/config
  • golangci-lint run --timeout=5m ./internal/provider/... ./internal/config/...

@octo-patch
octo-patch force-pushed the octo/20260708-add-target-provider-model-to-existing-provider-registry-recvoNoSYsJNk9 branch from ee16ead to 7ef9dd5 Compare July 15, 2026 14:24
Correct MiniMax-M3 input/output/cache-read prices to 0.6/2.4/0.12 per
million tokens and add price assertions to the registry test.
@octo-patch

Copy link
Copy Markdown
Author

Thanks for the review. I corrected the MiniMax-M3 registry pricing (input 0.6, output 2.4, cache-read 0.12 per million tokens) to match the provider spec and added price assertions to the registry test. I ran go vet, go test -race ./internal/provider/... ./internal/config/..., and go build ./... — all green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant