Music 1.0 or Music Router: which route for new Sume code?
Use POST /v1/music-router/generate for new code. Music 1.0 still works but resolves through the router; every router model bills the same fixed $0.125.
Use the router for new integrations
The Sume docs say Music 1.0 is being retired gradually: its routes keep working and keep job.model as sume/music-1.0, but every request now resolves through the Music Router as sume/music-auto. For new integrations, call POST /v1/music-router/generate.
What differs
| Topic | Music 1.0 | Music Router |
|---|---|---|
| Invoke URL | POST /v1/music-1.0/generate | POST /v1/music-router/generate |
| Model field | Not accepted | Optional: sume/music-auto, lyria-3.5, lyria-3-pro |
| Default engine | Lyria 3.5 via the router | sume/music-auto resolves to lyria-3.5 today and may move |
| Price | $0.125 per generation | Same fixed price per generation for every router model |
| Prompt limit | 5,000 characters | 5,000 characters |
Pin or not
sume/music-auto may move without notice. If a campaign needs the same engine for every cue, pin lyria-3.5 explicitly. job.request.routed_model names the engine that ran on both the router and the Music 1.0 routes, so you can verify what you got.
The catalog lists provider list prices per model for reference, but the docs state that every router model charges the fixed Music price, so do not budget by the list column.
Cost example
A 20-cue game soundtrack with three takes per cue is 60 generations, 60 x $0.125 = $7.50, whichever route or pinned model you call. See Music Router and Music 1.0.
Migration is small
Moving from Music 1.0 to the router is a URL change and, optionally, a model field. The request body keeps the same prompt, image_url, metadata, mode and webhook fields. Keep your idempotency keys and polling code, because both routes return jobs you poll at /v1/jobs.
Existing job.model values of sume/music-1.0 stay on old jobs, so dashboards that group by model will show both ids during the transition.
Choosing a pinned engine
Pinning matters if a client approved a sound. Lyria 3.5 is the current default behind sume/music-auto, and lyria-3-pro is also listed in the router. Because the fixed price applies to each router model per the docs, the choice is about sound and not about the bill. Test one prompt on each and keep the one you prefer.
Sources
More in Developers
- Music 1.0 to Music Router: what changes in your integration
Sume is retiring Music 1.0 gradually; every request already resolves through the Music Router. New code should call /v1/music-router/generate. What changes.
- Music API 400s: duration and negative_prompt, and the fix
Sume's Music Router returns 400 if you send duration, duration_seconds or a non-empty negative_prompt. The fix for each, and a request that passes validation.
- Music prompt limits: 1-5000 characters and no duration field
Sume's Music Router takes a 1 to 5000 character prompt and rejects duration. How to set length and sections in the prompt text, with a request.
- Nano Banana 2.1 4K batch: handle 200 and 202, reuse the key
A 4K Nano Banana 2.1 call can return 200 with the image or 202 with a job. A short Python handler, the retry rule, and what 4K costs: $0.20 per image on Sume.
Written by Sume