Skip to main content

MiniMax

Use this when your team already runs on MiniMax and you want that vendor family to stay explicit in Loong config instead of disappearing behind a generic compatibility route.

At A Glance

FieldValue
Built-in kindminimax
Provider groupDirect Hosted Providers
Protocol familyopenai_chat_completions
Feature familyopenai_compatible
Auth schemebearer
Credential envsMINIMAX_API_KEY
Aliasesminimax_compatible
Default base URLhttps://api.minimaxi.com
Request endpointhttps://api.minimaxi.com/v1/chat/completions
Models endpointhttps://api.minimaxi.com/v1/models

Minimal Config

active_provider = "minimax"

[providers.minimax]
kind = "minimax"
api_key = { env = "MINIMAX_API_KEY" }
model = "auto"

Verify It

loong doctor
loong list-models
loong ask --message "Say hello and name the active provider."
If list-models is unreliable for this account or region, pin an explicit provider.model or add preferred_models instead of leaving recovery implicit.

Auth And Routing Contract

ContractValue
Auth optionalno
Model probe auth optionalno
Default API key envMINIMAX_API_KEY
OAuth envnone
Primary request routehttps://api.minimaxi.com/v1/chat/completions
Primary model-catalog routehttps://api.minimaxi.com/v1/models

Region Endpoints

VariantBase URL
CNhttps://api.minimaxi.com
Globalhttps://api.minimax.io
MiniMax region endpoint: CN default (https://api.minimaxi.com); switch provider.base_url to https://api.minimax.io for Global accounts

Operator Notes

  • Reviewed onboarding fallback when model = "auto" cannot probe cleanly: MiniMax-M2.7.