Audio Lead Gen Tool

AI Music Entry

Adds one entry for soundtrack, voice cloning, and speech synthesis powered by the MiniMax audio runtime.

Ships as a dedicated public tool page.

Shares the same media task adapter as image and video.

Routes voice, speech, and music work through a unified MiniMax audio provider.

Beta

What this MVP adds

The goal is not a second standalone public music studio. It is a platform entry, a visible directory slot, and a real audio execution target.

Public Entry

Ships a dedicated /tools/ai-music page so the capability has a product-facing landing page.

MiniMax Audio Runtime

Routes AI music, voice clone, and speech synthesis through MiniMax while preserving the same platform submission and polling contract.

Directory Visibility

Makes AI music visible in both the capability directory and the public tools center instead of hiding it behind future planning notes.

View capability detail Back to tools

Platform capability

AI music now shares the unified media task adapter with image and video surfaces, while its audio provider is MiniMax.

Why ship the entry first

This phase solves visibility, discoverability, and runtime wiring first, then leaves room for a richer generation UI later.

FAQ

This page clarifies the entry point, runtime boundary, and integration contract before the richer UI lands.

Can this page already generate music directly in-browser?

This phase already wires the real platform entry, directory mapping, and unified task path. Audio execution now runs through MiniMax, while the richer public-page UX can keep improving afterward.

Why reuse the shared media runtime instead of building a separate music runtime?

Image, video, and music all behave like async media jobs. Reusing the same runtime keeps provider wiring, polling, and task-state handling consistent.

Which provider handles AI music jobs?

AI music, voice cloning, and speech synthesis route through MiniMax, while the video-focused capabilities continue to use RunningHub.