MiniMax shipped MiniMax-Music3 on August 13, and unlike most model drops that arrive with a paper and a shrug about inference, this one comes with weights, code, and three documented serving paths on day one. That distinction matters. You can actually deploy it — solo creators, indie studios, and mid-market teams alike — without waiting for a community port or a third-party wrapper to emerge.
The architecture is where things get interesting. Instead of the usual discrete-token decoding pipeline, MiniMax pairs a Hybrid-LM — an 8B Global LLM handling long-range structure and a 0.6B Local LLM handling per-frame detail — with a 2.4B flow-matching module that operates on the fused continuous hidden states of both models. The discrete tokenizer decoder never gets loaded at inference. The model card says the Global LLM is initialized from Qwen3-8B; the research post says Qwen3.5-8B. MiniMax hasn’t clarified, so treat that detail as unsettled.
The two-input design is genuinely practical. Lyrics come with section tags like [Verse] and [Chorus] on their own lines. A separate structured caption carries global metadata, vocal details, and arrangement notes. MiniMax also released a music-caption-rewriter agent skill that expands short descriptions into that three-part format offline. That’s the kind of tooling that separates a demo from a production asset.
The license has teeth, but they’re reasonable teeth. Commercial use is permitted with visible attribution to MiniMax-Music3 in the product UI. Cross $20 million in aggregate yearly revenue from those products, and you need prior written authorization. Hosts of third-party generation must implement safeguards against infringing outputs. For game studios, ad agencies, podcasters, and fitness apps, that’s workable. For anyone hoping to build a white-label music generation API on top of someone else’s model without attribution, it’s a non-starter — and that feels intentional given how aggressively the music industry has pursued AI companies over training data and output similarity. The open-weights move puts MiniMax in a different position than closed API providers when the inevitable copyright questions surface.
