Music Router price: one fixed $0.125 per track, 20 tracks cost $2.50

Sume's Music Router charges one fixed price per accepted generation whichever engine runs, regardless of prompt length. What 20 tracks cost and what to check.

4 min readSume
All posts

On Sume, a Music Router generation costs a fixed $0.125 per accepted job, whichever engine runs, and the price does not vary by prompt length or optional image conditioning. Twenty tracks cost $2.50 and two hundred cost $25.00, before any retries you choose to make.

What does the Music Router charge?

The Music Router docs say every Music Router model charges the fixed Music price per audio generation, and that the catalog lists the provider list price per model for reference only. The Music 1.0 docs put that fixed price at $0.125 USD per accepted generation, with no variation by prompt length or optional image conditioning.

Routable ids are sume/music-auto (the default), lyria-3.5 and lyria-3-pro. sume/music-auto picks the engine, Lyria 3.5 today, and the job reports the engine that ran in job.request.routed_model.

Music Router cost at the fixed price, from the Sume docs, read 2026-10-02
TracksCost at $0.125 each
1$0.125
8$1.00
20$2.50
100$12.50
200$25.00

Does choosing a pricier engine cost more?

Not according to the docs: the router charges the fixed Music price per generation across its models. The per-model provider list prices in the catalog are there for reference. That makes the engine choice a quality decision and not a budget one, which is unusual in this catalog, where video and image prices usually follow the model.

Do not infer more than the docs state. They do not promise the price stays fixed forever, so read it from GET /v1/catalog before a large run, as the docs advise for other media tools.

How do I budget a batch?

Multiply the track count by $0.125, then add a retry allowance. Submit with an Idempotency-Key so a retried request returns the original job and not a second charge, then poll status and read the audio artifact from result.artifacts[] where type is audio.

duration and duration_seconds are rejected on this route. Length is steered in the prompt, for example by asking for a two-minute track or writing section timestamps. Because the price is per generation and not per second, a longer requested track costs the same as a shorter one, but you cannot guarantee the length.

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: music-router-001" \
  -d '{"model": "sume/music-auto", "prompt": "Warm lo-fi hip hop, 84 BPM. A 30-second instrumental."}'

What does this price not cover?

It covers the generation only. Trimming, captions and timeline assembly are separate jobs with their own rates. Music 1.0 is retiring gradually, though its routes keep working and now resolve through the Music Router, so new code should call the router.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume