Models / Providers

MiniMax

Genesis'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:

Built-in catalog

Getting started

Choose your preferred auth method and follow the setup steps.

OAuth (Coding Plan)

Best for: quick setup with MiniMax Coding Plan via OAuth, no API key required.

International

Run onboarding

genesis onboard --auth-choice minimax-global-oauth

This authenticates against api.minimax.io.

Verify the model is available

genesis models list --provider minimax-portal

China

Run onboarding

genesis onboard --auth-choice minimax-cn-oauth

This authenticates against api.minimaxi.com.

Verify the model is available

genesis models list --provider minimax-portal

API key

Best for: hosted MiniMax with Anthropic-compatible API.

International

Run onboarding

genesis onboard --auth-choice minimax-global-api

This configures api.minimax.io as the base URL.

Verify the model is available

genesis models list --provider minimax

China

Run onboarding

genesis onboard --auth-choice minimax-cn-api

This configures api.minimaxi.com as the base URL.

Verify the model is available

genesis models list --provider minimax

Config example

{
  env: { MINIMAX_API_KEY: "sk-..." },
  agents: { defaults: { model: { primary: "minimax/MiniMax-M2.7" } } },
  models: {
    mode: "merge",
    providers: {
      minimax: {
        baseUrl: "https://api.minimax.io/anthropic",
        apiKey: "${MINIMAX_API_KEY}",
        api: "anthropic-messages",
        models: [
          {
            id: "MiniMax-M2.7",
            name: "MiniMax M2.7",
            reasoning: true,
            input: ["text"],
            cost: { input: 0.3, output: 1.2, cacheRead: 0.06, cacheWrite: 0.375 },
            contextWindow: 204800,
            maxTokens: 131072,
          },
          {
            id: "MiniMax-M2.7-highspeed",
            name: "MiniMax M2.7 Highspeed",
            reasoning: true,
            input: ["text"],
            cost: { input: 0.6, output: 2.4, cacheRead: 0.06, cacheWrite: 0.375 },
            contextWindow: 204800,
            maxTokens: 131072,
          },
        ],
      },
    },
  },
}

Configure via genesis configure

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

Launch the wizard

genesis configure

Select Model/auth

Choose Model/auth from the menu.

Choose a MiniMax auth option

Pick one of the available MiniMax options:

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, Genesis materializes MiniMax-M2.7 and MiniMax-M2.7-highspeed as text-only chat models. Image understanding is exposed separately through the plugin-owned MiniMax-VL-01 media provider.

Text-to-speech

The bundled minimax plugin registers MiniMax T2A v2 as a speech provider for messages.tts.

• Default TTS model: speech-2.8-hd
• Default voice: English_expressive_narrator
• Normal audio attachments stay MP3.
• Voice-note targets such as Feishu and Telegram are transcoded from MiniMax MP3 to 48kHz Opus with ffmpeg, because the Feishu/Lark file API only accepts file_type: "opus" for native audio messages.
• MiniMax T2A accepts fractional speed and vol, but pitch is sent as an integer; Genesis truncates fractional pitch values before the API request.

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+",
      },
    },
  },
}

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",
      },
    },
  },
}

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 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.*.

Advanced configuration

Configuration options

Thinking defaults

On api: "anthropic-messages", Genesis 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 on or params.fastMode: true rewrites MiniMax-M2.7 to MiniMax-M2.7-highspeed on the Anthropic-compatible stream path.

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.

{
  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 details

• Coding Plan usage API: https://api.minimaxi.com/v1/api/openplatform/coding_plan/remains (requires a coding plan key).
• Genesis 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 Genesis inverts them. Count-based fields win when present.
• When the API returns model_remains, Genesis 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 text-only model definitions for both M2.7 variants
• Image understanding uses the plugin-owned MiniMax-VL-01 media provider
• Update pricing values in models.json if you need exact cost tracking
• Use genesis models list to confirm the current provider id, then switch with genesis models set minimax/MiniMax-M2.7 or genesis models set minimax-portal/MiniMax-M2.7

Troubleshooting

Accordion

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 genesis 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:

genesis models list

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.