Pin AI music model ids: music_v2_5, v6, lyria-3.5 and sume/music-auto

Pin the model id in your music config instead of relying on a vendor default, and log the engine that actually ran. ElevenLabs lists music_v2_5, music_v2 and music_v1 in its API docs; Suno names v6, v6-wild and v6-mini; Google lists lyria-3.5. On Sume, sume/music-auto lets Sume pick (Lyria 3.5 today) and lyria-3.5 pins it; the job records the engine in job.request.routed_model.

The ids, by vendor

ElevenLabs made Music v2.5 the default for prompted and reference generation, and its announcement says Music v2 remains available. The API docs page lists the API ids. Suno's help page names its v6 models, and the v6 post says previous models will be retired. Google's pricing page lists the Lyria ids.

Rules for a stable integration

A default is a moving target: ElevenLabs made v2.5 the ElevenMusic default on September 11, 2026, and Suno plans to retire earlier models. A pipeline that omits the model silently changes behaviour when the vendor flips it.

• Always send an explicit model id where the vendor allows it.
• Store the id you requested and the id that ran.
• Treat "preview" ids as short-lived and re-check them monthly.
• Re-audition a brief when the default changes, rather than assuming equivalence.

What this looks like on Sume

The Music Router docs say that job.model echoes the requested id and that job.request.routed_model names the engine that ran, so the two fields together give you the "requested vs ran" pair. Pinning lyria-3.5 makes a campaign repeatable at the engine level, though results still vary between calls because there is no seed. GET /v1/music-router/models returns the catalog, so validate your config against it rather than against a blog table.

Write it down

Put the id table in your repository and date it. When a vendor retires a model or changes a default, you will know which campaigns used it. The Music 1.0 page notes that Music 1.0 routes now resolve through the router, so older integrations can keep sume/music-1.0 while new ones call the router. Poll and fetch jobs as described in Jobs and results.