Music 1.0 is retiring: moving to the Music Router in one line

Is Sume Music 1.0 going away? It is retiring gradually, per both docs pages. Its routes keep working and keep job.model = sume/music-1.0, but every request now resolves through the Music Router (sume/music-auto). New integrations should call POST /v1/music-router/generate. I found no shutdown date in the docs, and this post does not give one.

The migration is mostly a URL change, plus one optional field.

What changes

The router takes the same body as Music 1.0, plus an optional model. Leave it off and you get sume/music-auto, which is Lyria 3.5 today.

What does not change

The request fields are the same: prompt (1 to 5000 characters), optional image_url, metadata, mode, webhook_url and wait_timeout_seconds. duration and duration_seconds are still rejected, and a non-empty negative_prompt is still a 400. The result still carries an audio artifact in result.artifacts[].

The one-line diff

Swap the path and, if you want to pin an engine, add model.

curl -X POST https://api.sume.com/v1/music-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: migrate-001" \
  -d '{"prompt":"Warm lo-fi hip hop, 84 BPM, C minor. A 30-second track. Instrumental, no vocals."}'

Pricing

The Music 1.0 page lists a fixed $0.125 per accepted generation, and the router page says every Music Router model charges the fixed Music price per audio generation. Confirm the live number in GET /v1/catalog.