Does Lyria 3.5 audio carry a SynthID watermark?

Yes: Google's Gemini API music docs say Lyria audio carries a SynthID watermark. The Sume docs I read do not describe watermarking either way.

4 min readSume
All posts

Yes, per the Gemini API music generation docs read on 2026-10-04: audio from Lyria carries a SynthID watermark. The Sume Music Router docs I read do not mention watermarking, so I cannot say what applies to audio served from media.sume.com.

What is documented

Lyria 3.5 output facts from the Gemini docs (read 2026-10-04)
ItemDetail
WatermarkSynthID
Default formatMP3
WAVresponse_format with type audio
Image inputUp to 10 images plus text
EditingSingle-turn, no iterative editing
Artist voicesPrompts that ask for an artist's voice are blocked

What to do with this

  • Disclose AI music where a platform requires it.
  • Do not strip or re-encode away provenance in a way a platform forbids.
  • Ask in writing if your use depends on the watermark surviving.

Through Sume

The router returns one audio artifact, typically audio/mpeg, and job.request.routed_model names the engine that ran. Read it on the job to know whether Lyria produced the track.

curl https://api.sume.com/v1/jobs/JOB_ID/result \
  -H "Authorization: Bearer $SUME_API_KEY"

Gap

Whether a watermark persists through Sume's delivery pipeline is not something I read; test it with the detector you rely on.

Sources

Related posts

More in Models

All Models posts

Written by Sume