Skip to main content
FluffBuzz’s MiniMax provider defaults to MiniMax M2.7. MiniMax also provides:
  • Bundled speech synthesis via T2A v2
  • Bundled image understanding via MiniMax-VL-01
  • Bundled music generation via music-2.5+
  • Bundled web_search through the MiniMax Coding Plan search API
Provider split:
Provider IDAuthCapabilities
minimaxAPI keyText, image generation, image understanding, speech, web search
minimax-portalOAuthText, image generation, image understanding

Built-in catalog

ModelTypeDescription
MiniMax-M2.7Chat (reasoning)Default hosted reasoning model
MiniMax-M2.7-highspeedChat (reasoning)Faster M2.7 reasoning tier
MiniMax-VL-01VisionImage understanding model
image-01Image generationText-to-image and image-to-image editing
music-2.5+Music generationDefault music model
music-2.5Music generationPrevious music generation tier
music-2.0Music generationLegacy music generation tier
MiniMax-Hailuo-2.3Video generationText-to-video and image reference flows

Getting started

Choose your preferred auth method and follow the setup steps.
Best for: quick setup with MiniMax Coding Plan via OAuth, no API key required.
1

Run onboarding

fluffbuzz onboard --auth-choice minimax-global-oauth
This authenticates against api.minimax.io.
2

Verify the model is available

fluffbuzz models list --provider minimax-portal
OAuth setups use the minimax-portal provider id. Model refs follow the form minimax-portal/MiniMax-M2.7.
Referral link for MiniMax Coding Plan (10% off): MiniMax Coding Plan

Configure via fluffbuzz configure

Use the interactive config wizard to set MiniMax without editing JSON:
1

Launch the wizard

fluffbuzz configure
2

Select Model/auth

Choose Model/auth from the menu.
3

Choose a MiniMax auth option

Pick one of the available MiniMax options:
Auth choiceDescription
minimax-global-oauthInternational OAuth (Coding Plan)
minimax-cn-oauthChina OAuth (Coding Plan)
minimax-global-apiInternational API key
minimax-cn-apiChina API key
4

Pick your default model

Select your default model when prompted.

Capabilities

Image generation

The MiniMax plugin registers the image-01 model for the image_generate tool. It supports:
  • Text-to-image generation with aspect ratio control
  • Image-to-image editing (subject reference) with aspect ratio control
  • Up to 9 output images per request
  • Up to 1 reference image per edit request
  • Supported aspect ratios: 1:1, 16:9, 4:3, 3:2, 2:3, 3:4, 9:16, 21:9
To use MiniMax for image generation, set it as the image generation provider:
{
  agents: {
    defaults: {
      imageGenerationModel: { primary: "minimax/image-01" },
    },
  },
}
The plugin uses the same MINIMAX_API_KEY or OAuth auth as the text models. No additional configuration is needed if MiniMax is already set up. Both minimax and minimax-portal register image_generate with the same image-01 model. API-key setups use MINIMAX_API_KEY; OAuth setups can use the bundled minimax-portal auth path instead. When onboarding or API-key setup writes explicit models.providers.minimax entries, FluffBuzz materializes MiniMax-M2.7 and MiniMax-M2.7-highspeed with input: ["text", "image"]. The built-in bundled MiniMax text catalog itself stays text-only metadata until that explicit provider config exists. Image understanding is exposed separately through the plugin-owned MiniMax-VL-01 media provider.
See Image Generation for shared tool parameters, provider selection, and failover behavior.

Music generation

The bundled minimax plugin also registers music generation through the shared music_generate tool.
  • Default music model: minimax/music-2.5+
  • Also supports minimax/music-2.5 and minimax/music-2.0
  • Prompt controls: lyrics, instrumental, durationSeconds
  • Output format: mp3
  • Session-backed runs detach through the shared task/status flow, including action: "status"
To use MiniMax as the default music provider:
{
  agents: {
    defaults: {
      musicGenerationModel: {
        primary: "minimax/music-2.5+",
      },
    },
  },
}
See Music Generation for shared tool parameters, provider selection, and failover behavior.

Video generation

The bundled minimax plugin also registers video generation through the shared video_generate tool.
  • Default video model: minimax/MiniMax-Hailuo-2.3
  • Modes: text-to-video and single-image reference flows
  • Supports aspectRatio and resolution
To use MiniMax as the default video provider:
{
  agents: {
    defaults: {
      videoGenerationModel: {
        primary: "minimax/MiniMax-Hailuo-2.3",
      },
    },
  },
}
See Video Generation for shared tool parameters, provider selection, and failover behavior.

Image understanding

The MiniMax plugin registers image understanding separately from the text catalog:
Provider IDDefault image model
minimaxMiniMax-VL-01
minimax-portalMiniMax-VL-01
That is why automatic media routing can use MiniMax image understanding even when the bundled text-provider catalog still shows text-only M2.7 chat refs. The MiniMax plugin also registers web_search through the MiniMax Coding Plan search API.
  • Provider id: minimax
  • Structured results: titles, URLs, snippets, related queries
  • Preferred env var: MINIMAX_CODE_PLAN_KEY
  • Accepted env alias: MINIMAX_CODING_API_KEY
  • Compatibility fallback: MINIMAX_API_KEY when it already points at a coding-plan token
  • Region reuse: plugins.entries.minimax.config.webSearch.region, then MINIMAX_API_HOST, then MiniMax provider base URLs
  • Search stays on provider id minimax; OAuth CN/global setup can still steer region indirectly through models.providers.minimax-portal.baseUrl
Config lives under plugins.entries.minimax.config.webSearch.*.
See MiniMax Search for full web search configuration and usage.

Advanced configuration

OptionDescription
models.providers.minimax.baseUrlPrefer https://api.minimax.io/anthropic (Anthropic-compatible); https://api.minimax.io/v1 is optional for OpenAI-compatible payloads
models.providers.minimax.apiPrefer anthropic-messages; openai-completions is optional for OpenAI-compatible payloads
models.providers.minimax.apiKeyMiniMax API key (MINIMAX_API_KEY)
models.providers.minimax.modelsDefine id, name, reasoning, contextWindow, maxTokens, cost
agents.defaults.modelsAlias models you want in the allowlist
models.modeKeep merge if you want to add MiniMax alongside built-ins
On api: "anthropic-messages", FluffBuzz injects thinking: { type: "disabled" } unless thinking is already explicitly set in params/config.This prevents MiniMax’s streaming endpoint from emitting reasoning_content in OpenAI-style delta chunks, which would leak internal reasoning into visible output.
/fast on or params.fastMode: true rewrites MiniMax-M2.7 to MiniMax-M2.7-highspeed on the Anthropic-compatible stream path.
Best for: keep your strongest latest-generation model as primary, fail over to MiniMax M2.7. Example below uses Opus as a concrete primary; swap to your preferred latest-gen primary model.
{
  env: { MINIMAX_API_KEY: "sk-..." },
  agents: {
    defaults: {
      models: {
        "anthropic/claude-opus-4-6": { alias: "primary" },
        "minimax/MiniMax-M2.7": { alias: "minimax" },
      },
      model: {
        primary: "anthropic/claude-opus-4-6",
        fallbacks: ["minimax/MiniMax-M2.7"],
      },
    },
  },
}
  • Coding Plan usage API: https://api.minimaxi.com/v1/api/openplatform/coding_plan/remains (requires a coding plan key).
  • FluffBuzz normalizes MiniMax coding-plan usage to the same % left display used by other providers. MiniMax’s raw usage_percent / usagePercent fields are remaining quota, not consumed quota, so FluffBuzz inverts them. Count-based fields win when present.
  • When the API returns model_remains, FluffBuzz prefers the chat-model entry, derives the window label from start_time / end_time when needed, and includes the selected model name in the plan label so coding-plan windows are easier to distinguish.
  • Usage snapshots treat minimax, minimax-cn, and minimax-portal as the same MiniMax quota surface, and prefer stored MiniMax OAuth before falling back to Coding Plan key env vars.

Notes

  • Model refs follow the auth path:
    • API-key setup: minimax/<model>
    • OAuth setup: minimax-portal/<model>
  • Default chat model: MiniMax-M2.7
  • Alternate chat model: MiniMax-M2.7-highspeed
  • Onboarding and direct API-key setup write explicit model definitions with input: ["text", "image"] for both M2.7 variants
  • The bundled provider catalog currently exposes the chat refs as text-only metadata until explicit MiniMax provider config exists
  • Update pricing values in models.json if you need exact cost tracking
  • Use fluffbuzz models list to confirm the current provider id, then switch with fluffbuzz models set minimax/MiniMax-M2.7 or fluffbuzz models set minimax-portal/MiniMax-M2.7
Referral link for MiniMax Coding Plan (10% off): MiniMax Coding Plan
See Model providers for provider rules.

Troubleshooting

This usually means the MiniMax provider is not configured (no matching provider entry and no MiniMax auth profile/env key found). A fix for this detection is in 2026.1.12. Fix by:
  • Upgrading to 2026.1.12 (or run from source main), then restarting the gateway.
  • Running fluffbuzz configure and selecting a MiniMax auth option, or
  • Adding the matching models.providers.minimax or models.providers.minimax-portal block manually, or
  • Setting MINIMAX_API_KEY, MINIMAX_OAUTH_TOKEN, or a MiniMax auth profile so the matching provider can be injected.
Make sure the model id is case-sensitive:
  • API-key path: minimax/MiniMax-M2.7 or minimax/MiniMax-M2.7-highspeed
  • OAuth path: minimax-portal/MiniMax-M2.7 or minimax-portal/MiniMax-M2.7-highspeed
Then recheck with:
fluffbuzz models list
More help: Troubleshooting and FAQ.

Model selection

Choosing providers, model refs, and failover behavior.

Image generation

Shared image tool parameters and provider selection.

Music generation

Shared music tool parameters and provider selection.

Video generation

Shared video tool parameters and provider selection.

MiniMax Search

Web search configuration via MiniMax Coding Plan.

Troubleshooting

General troubleshooting and FAQ.