Spotify AI credits in Song Credits: DDEX disclosure for AI music
Spotify shows AI credits in Song Credits only when your label or distributor submits the DDEX disclosure. No credit does not mean no AI. Keep job notes.

Spotify shows AI credits for contributions like vocals, lyrics or production in Song Credits on mobile, but only where the artist disclosed through a label or distributor using the DDEX standard. Spotify's page says the absence of a credit does not mean AI was not used.
From the Spotify newsroom page, read 2026-10-01. The disclosure travels through your distributor, so the practical work is keeping accurate notes about how a track was made.
What did Spotify announce?
The page describes an industry standard for AI disclosures in music credits, developed through DDEX, that Spotify will display as information arrives from labels, distributors and music partners. On April 16 it launched a beta feature that lets artists share how they used AI. Spotify also says it is not about down-ranking tracks for disclosing.
| Item | What the page says |
|---|---|
| Where it shows | Song Credits on mobile |
| Examples of credits | Vocals, lyrics or production |
| How it gets there | Submitted through labels, distributors and music partners |
| Limit | Not all distributors let artists disclose yet |
| No credit | Does not mean AI was not used |
What does a Sume Music job give me to fill in?
Music 1.0 runs on Google Lyria 3.5 and generates structured songs from a prompt. The Spotify page lists AI-generated vocals, instrumentation or post-production as the kinds of contribution to indicate, so a song straight from a prompt would have AI in each of those parts unless you replaced them. Your distributor's form defines the exact fields.
Where do I keep my own record?
Use the metadata field on the job, described as "Caller metadata stored on the job; not sent to the provider." Put the track id and what you did: which parts were generated, which you recorded yourself. The job keeps the note next to the output.
curl -X POST https://api.sume.com/v1/music-router/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{"prompt":"Mid-tempo indie rock, 108 BPM, E minor. Instrumental, no vocals.","metadata":{"track":"T-102","ai_parts":"instrumentation,production"}}'Which endpoint is current?
The docs say Music 1.0 is retiring gradually, routes keep working, and new integrations should call POST /v1/music-router/generate. Compare with the AI Persona badge, a separate Spotify mechanism.
What should I do before submitting?
Ask your distributor whether it supports the DDEX AI disclosure, fill it truthfully per track, and keep the job record. Because Spotify depends on disclosure, accuracy is on you. This is not legal advice.
Sources
Related posts
More in Use cases
- Holiday jingle for ads: Spotify says listening starts in October
Spotify reports holiday listening already underway on Oct 1. Make a holiday music bed for an ad with the Music Router, steering length in the prompt.
- Spotify video podcast aspect ratio: any, but shown in 16:9
Spotify accepts any aspect ratio for video podcasts but may letterbox it in 16:9. Deliver a true 16:9 frame with video-trim output or Timeline contain.
- Steam bundle header 707x232: what an AI image can hit
Steam wants a 707x232 bundle header. Sume's custom sizes cap at 3:1, and 707x232 is wider, so generate near it and finish the exact crop yourself.
- Steam Library Capsule 600x900: below the image pixel floor
Steam's Library Capsule is 600x900, only 540,000 pixels, under Sume's 655,360-pixel floor. Generate 800x1200 and downscale, or route through Timeline.
Written by Sume