Vendor pages to read before AI music goes in an ad
The vendor pages that answer commercial-use questions for Suno v6, ElevenLabs Music v2.5 and Google Lyria 3.5, and which question each answers, read 2026-10-04.
Most arguments about AI music licensing come from secondary articles. The vendor's own pages answer the questions that matter to an ad buyer: who may use output commercially, what the plan includes, what you may not type into the prompt, and what the model costs. Read these five before you ship: Suno's terms and pricing, ElevenLabs' music terms and API pricing, and Google's Gemini API pricing page.
Which page answers which question
The table maps each question to a page. All were read on 2026-10-04; page contents can change.
| Question | Suno | ElevenLabs | Google Lyria |
|---|---|---|---|
| Who may use output commercially? | suno.com/terms and pricing: Pro and Premier, with an approved download | elevenlabs.io/music-terms: depends on plan and use case | Check Google's terms for your use; the pricing page covers cost only |
| What does it cost? | suno.com/pricing: $8 Pro, $24 Premier per month | elevenlabs.io/pricing/api: $0.15 per minute of music | ai.google.dev pricing: $0.08 per song for Lyria 3.5 |
| What can't I send? | Read the terms for input and output restrictions | Terms: no artist names, song, album, publisher or label names, no substantial lyrics of a particular song | Google's music guide (not in this list) screens prompts; see our Lyria post |
| Which model is current? | Check Suno's own announcements | Pricing page lists one Music product | Pricing page: Lyria 3.5, with Lyria 3 Clip and Pro as legacy |
Read the sources in this order
Start with the Suno terms and ElevenLabs music terms, since rights live there. Then read the Suno pricing and ElevenLabs API pricing pages for plan gates and costs. Finish with Google's Gemini API pricing page for Lyria, where the free tier is not available for these models.
- Copy the clause, the URL and the date into your asset log.
- Re-read before each campaign: the pages change.
- Treat blog summaries, including this one, as pointers to the vendor page.
Where Sume fits
Sume's pages describe Sume. The Music Router docs cover routing, request fields, and pricing for the router, and they do not restate what Google, Suno or ElevenLabs permit. So a Sume track needs two reads: the Sume terms for your use of the platform, and the terms of the engine named in job.request.routed_model. Record both with the job metadata described in Music 1.0.
None of this is legal advice. When a page is ambiguous, ask the vendor in writing.
Sources
Related posts
More in Use cases
- Vietnam AI Law Article 11: labelling real people, real events
Under Vietnam's AI Law, deployers must label AI media that imitates a real person's face or voice or recreates a real event. Art and film get a softer rule.
- Vietnam AI Law Article 11: machine-readable marks for AI media
Vietnam's Law No. 134/2025/QH15, in force 1 March 2026, makes AI providers mark audio, image and video in machine-readable form. Sume docs show no such mark.
- Voicemail drop: pick immediate or delayed detection
ElevenLabs added voicemail detection for Twilio calls with immediate and delayed modes. Record the message ahead of time with Sume's tts_create and drop it.
- Walmart items with under 15 reviews: add a how-to-use clip
Walmart widened its Recognized Reviewer Program to items with under 15 reviews. While reviews build, a short how-to clip made with Sume can help.
Written by Sume