The argument about AI music has quietly stopped being about policy and started being about a checkbox. Two of the biggest DSPs now expect that checkbox to travel inside your metadata, and the place it gets filled in is your distributor’s upload flow.
DSP means digital service provider, the streaming platforms like Spotify and Apple Music. Here is what actually shipped, and why it lands on distributors before it lands on artists.
What went live in the last year
Spotify adopted an industry AI disclosure standard in September 2025, letting creators flag AI involvement across five categories: vocals, instrumentation, composition, post-production, and lyrics, per Music Ally.
That flag became visible on April 16, 2026, when Spotify’s AI Credits started appearing in the Song Credits panel on mobile, in the same box that already lists songwriters and producers.
Apple Music followed in March 2026 with Transparency Tags, covering four elements: Artwork, Track, Composition, and Music Video. Music Business Worldwide reported the tags are optional now but will be required on new deliveries going forward.
The word Apple has not defined
Apple says to tag when a “material portion” of a track uses AI. It has not defined “material,” as Billboard noted.
That gap sounds academic until you are the one uploading. A producer who ran a stem through an AI mastering assistant has no clear instruction. Neither does an artist who generated one bridge and performed everything else live.
The guessing does not happen at the DSP. It happens at the point of delivery, which is your distributor.
Why this is a distribution problem first
All of this rides on DDEX. DDEX means Digital Data Exchange, the international standards body whose format most distributors use to package a release before sending it to a platform.
The AI disclosure lives as fields inside that DDEX package. If your distributor’s upload flow does not expose those fields, you cannot declare anything, and your delivery ships blank.
Blank has two costs. On Spotify, an AI-assisted track that should carry a credit arrives looking fully human, which is exactly the mislabeling both platforms say they are trying to end.
On Apple, once tags move from optional to required, a delivery that cannot carry them is a delivery at risk of rejection or a correction cycle. That is lost release-day momentum you do not get back.
Who can actually pass the fields through
Support is uneven. DistroKid has the disclosure fields live, while Believe, CD Baby, FUGA, IDOL, Amuse, and Empire have been rolling them out in stages, per coverage aggregated across LabelGrid.
“Rolling out in stages” is the phrase to watch. It means the field may be missing from your dashboard on the exact week you need it, and no upload screen will warn you it is absent.
What indie artists and labels should check this quarter
- Open your distributor’s upload flow and confirm it has explicit AI disclosure fields, not a single yes-or-no box.
- Check that the fields map to the five Spotify categories and the four Apple tag types, so one declaration feeds both.
- Ask your distributor, in writing, whether it delivers via a DDEX-native pipeline or a manual re-key. Manual re-key is where fields get dropped.
- For catalog already live, ask how you push a disclosure update to a release that shipped before the fields existed.
- Document your own AI use per track now, while you remember it. You will not remember in a year when a tag becomes mandatory.
This is the unglamorous part of the AI debate, and it is the part that decides whether your metadata is correct. A distributor that is DDEX-native and exposes the disclosure fields in the upload box, the way InterSpace Distribution and its ToneGrid platform are built to, turns a compliance headache into a checkbox you tick once.
The labeling era is not coming. It arrived in April, and it grades on delivery.
