You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Does it support the "Token" plan or only the standard API key? #1
Thanks for asking. The integration has no separate “Token Plan” authentication mode: it sends the value entered in the API Key field as Authorization: Bearer to MiniMax’s native voice-list and WebSocket TTS endpoints.
MiniMax currently lists Speech 2.8 as included in Token Plan and provides a Token Plan subscription key (sk-cp…). You can try entering that subscription key in the integration’s normal API Key field; there are no additional configuration fields or changes required. Use the appropriate region and select a voice as usual.
Please note that a Token Plan subscription key and a standard pay-as-you-go API key are separate credentials. Token Plan compatibility with these specific native voice endpoints has not yet been independently tested by this integration, so consider this best-effort support for now.
If setup validation or TTS fails, please share the redacted error message, selected region, and model/voice ID (never the key). I can then investigate and document or add explicit support if MiniMax requires a different flow.
Activity
AndrewSpec commentedon Oct 18, 2026
Thanks for asking. The integration has no separate “Token Plan” authentication mode: it sends the value entered in the API Key field as Authorization: Bearer to MiniMax’s native voice-list and WebSocket TTS endpoints.
MiniMax currently lists Speech 2.8 as included in Token Plan and provides a Token Plan subscription key (sk-cp…). You can try entering that subscription key in the integration’s normal API Key field; there are no additional configuration fields or changes required. Use the appropriate region and select a voice as usual.
Please note that a Token Plan subscription key and a standard pay-as-you-go API key are separate credentials. Token Plan compatibility with these specific native voice endpoints has not yet been independently tested by this integration, so consider this best-effort support for now.
If setup validation or TTS fails, please share the redacted error message, selected region, and model/voice ID (never the key). I can then investigate and document or add explicit support if MiniMax requires a different flow.