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.

4 min readSume
All posts

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.

Spotify AI credits beta, from the Spotify newsroom page read 2026-10-01.
ItemWhat the page says
Where it showsSong Credits on mobile
Examples of creditsVocals, lyrics or production
How it gets thereSubmitted through labels, distributors and music partners
LimitNot all distributors let artists disclose yet
No creditDoes 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

All Use cases posts

Written by Sume