Lyria 3.5 pricing: what a song costs on Google and on Sume

Lyria 3.5 costs $0.08 per song on Google's Gemini API, on the paid tier only. Sume charges its own fixed music price, $0.125 per audio, for each generation through the Music Router, plus a 5.5% agent fee by default. The two are separate rate cards with different terms, so read both against your volume.

Google's prices are from its Gemini API pricing page and Sume's from API pricing and the Music Router docs, read 2026-09-29.

What does Google charge for Lyria?

Google prices music per request, not per token. Its page lists three music models, all on the paid tier with no free tier:

What does Sume charge?

The Music Router docs say every Music Router model charges the fixed music price per audio generation, and the catalog at GET /v1/music-router/models lists each model's provider list price for reference. The rate card row is $0.125 per audio. The price does not vary with prompt length or with an image input.

• Each generation counts, including takes you discard.
• The 5.5% agent fee is added by default, as on other Sume rates.
• There is no charge line for length; steer length in the prompt.

How do I see the price before I run a job?

Ask the catalog. GET /v1/music-router/models returns, for each routable id, a pricing object with the list price and the billable price per audio.

curl https://api.sume.com/v1/music-router/models \
  -H "Authorization: Bearer $SUME_API_KEY"

Which one should I budget against?

Budget against the API you will actually call. If you call Google directly, use Google's per-song price and its paid-tier terms. If you call Sume, use the Sume row: it also covers the job envelope, hosted media.sume.com audio and the same key you use for video, image and speech. Neither page promises a price that will not change, so read the live page when you plan.