- Bundled speech synthesis via T2A v2
- Bundled image understanding via
MiniMax-VL-01 - Bundled music generation via
music-2.5+ - Bundled
web_searchthrough the MiniMax Coding Plan search API
Built-in catalog
Getting started
Choose your preferred auth method and follow the setup steps.- OAuth (Coding Plan)
- API key
Best for: quick setup with MiniMax Coding Plan via OAuth, no API key required.This authenticates against
- International
- China
1
Run onboarding
api.minimax.io.2
Verify the model is available
OAuth setups use the
minimax-portal provider id. Model refs follow the form minimax-portal/MiniMax-M2.7.Configure via fluffbuzz configure
Use the interactive config wizard to set MiniMax without editing JSON:
1
Launch the wizard
2
Select Model/auth
Choose Model/auth from the menu.
3
Choose a MiniMax auth option
Pick one of the available MiniMax options:
4
Pick your default model
Select your default model when prompted.
Capabilities
Image generation
The MiniMax plugin registers theimage-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
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 bundledminimax plugin also registers music generation through the shared
music_generate tool.
- Default music model:
minimax/music-2.5+ - Also supports
minimax/music-2.5andminimax/music-2.0 - Prompt controls:
lyrics,instrumental,durationSeconds - Output format:
mp3 - Session-backed runs detach through the shared task/status flow, including
action: "status"
See Music Generation for shared tool parameters, provider selection, and failover behavior.
Video generation
The bundledminimax 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
aspectRatioandresolution
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:
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.
Web search
The MiniMax plugin also registersweb_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_KEYwhen it already points at a coding-plan token - Region reuse:
plugins.entries.minimax.config.webSearch.region, thenMINIMAX_API_HOST, then MiniMax provider base URLs - Search stays on provider id
minimax; OAuth CN/global setup can still steer region indirectly throughmodels.providers.minimax-portal.baseUrl
plugins.entries.minimax.config.webSearch.*.
See MiniMax Search for full web search configuration and usage.
Advanced configuration
Configuration options
Configuration options
Thinking defaults
Thinking defaults
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 mode
Fast mode
/fast on or params.fastMode: true rewrites MiniMax-M2.7 to MiniMax-M2.7-highspeed on the Anthropic-compatible stream path.Fallback example
Fallback example
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.
Coding Plan usage details
Coding Plan usage details
- 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
% leftdisplay used by other providers. MiniMax’s rawusage_percent/usagePercentfields 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 fromstart_time/end_timewhen 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, andminimax-portalas 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>
- API-key setup:
- 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.jsonif you need exact cost tracking - Use
fluffbuzz models listto confirm the current provider id, then switch withfluffbuzz models set minimax/MiniMax-M2.7orfluffbuzz models set minimax-portal/MiniMax-M2.7
See Model providers for provider rules.
Troubleshooting
"Unknown model: minimax/MiniMax-M2.7"
"Unknown model: minimax/MiniMax-M2.7"
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 configureand selecting a MiniMax auth option, or - Adding the matching
models.providers.minimaxormodels.providers.minimax-portalblock manually, or - Setting
MINIMAX_API_KEY,MINIMAX_OAUTH_TOKEN, or a MiniMax auth profile so the matching provider can be injected.
- API-key path:
minimax/MiniMax-M2.7orminimax/MiniMax-M2.7-highspeed - OAuth path:
minimax-portal/MiniMax-M2.7orminimax-portal/MiniMax-M2.7-highspeed
More help: Troubleshooting and FAQ.
Related
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.