minimax

minimaxPreset() in tui/internal/preset/preset.go ships provider minimax, exact model MiniMax-M3, and MINIMAX_API_KEY at the Anthropic-compatible regional endpoint https://api.minimaxi.com/anthropic (CN default) or https://api.minimax.io/anthropic (INTL). Its manifest explicitly wires vision.

The TUI preset editor's base_url row offers three options (ProviderRegionURLs["minimax"]):

• CN — https://api.minimaxi.com/anthropic (the template default).
• INTL — https://api.minimax.io/anthropic.
• OpenCode Go — https://opencode.ai/zen/go/v1. This is the only row

that implies a credential: selecting it sets api_key_env to OPENCODE_GO_API_KEY (the shared OpenCode Go account) and saving keeps that slot instead of minting a region-suffixed one.

CN and INTL imply no api_key_env, so cycling between them preserves whatever slot the host stamped (MINIMAX_CN_1_API_KEY, MINIMAX_INTL_1_API_KEY). Cycling off OpenCode Go restores the slot that was in place before it was selected, so the choice is reversible.

Template-specific settings

The model picker ships the latest two M-series generations only — MiniMax-M3 and MiniMax-M2.7 with its -highspeed variant. Per the TUI's model-curation rule (tui/CONTRACT.md) the older MiniMax-M2.5 / MiniMax-M2.1 / MiniMax-M2 ids are no longer selectable; a saved preset already pinned to one keeps working, the TUI just will not offer it again.

MiniMax-M3 natively accepts image/video content blocks on that same endpoint; this native path does not depend on an MCP or a separate plan. Both shipped generations are recorded as image-capable in modelHasVision.

MiniMax also publishes the separate optional MiniMax-Coding-Plan-MCP, package minimax-coding-plan-mcp, whose understand_image tool is available through manual install/client registration. The setup guide requires a Token Plan seat or purchased Credits, and the MCP is not auto-wired into this TUI preset. Keep this tool path distinct from native M3 vision. The similarly named community tomlee2013/minimax-mcp-vision project is not official.

Read the official Anthropic-compatible API documentation and Token Plan MCP guide for current details. Do not silently switch providers or auto-load/invoke an MCP when the native route fails. Verify the manifest in TUI source after template changes.

Operations

For base URL/API-compat/model/capability declaration shape versus credentials, see reference/operations/endpoint-capabilities/SKILL.md.