A DDEX-built credit standard is how Spotify's AI labels arrive

What happened

In its 25 September 2025 announcement, Spotify states it is “helping develop and will support the new industry standard for AI disclosures in music credits, developed through DDEX,” naming nineteen distributor and label-services partners working on it, including DistroKid, CD Baby, Believe, FUGA and EMPIRE. Spotify adds that a beta version of the resulting AI-credit feature launched on 16 April 2025, and that “tens of thousands of AI credits” were being submitted daily by the time of the September post. DDEX itself is a decades-old standards body whose Electronic Release Notification (ERN) message suite is the format labels and distributors already use to send release metadata to streaming services.

What the documents say

DDEX's own description of ERN states that its main message, the NewReleaseMessage, carries metadata about a release and about “all the resources… contained within a release,” sent by a label or distributor to a digital service provider. Spotify's post does not specify a field name or an ERN version number, and no DDEX document opened for this article confirms a specific technical addition, so that detail is not asserted here. What is documented is the workflow: an artist discloses an AI-made contribution to their distributor, the distributor submits it in the delivery file, and Spotify displays it in Song Credits. Spotify states the credit is per role, not per track, and that “the absence of a credit doesn't mean AI wasn't used,” because disclosure depends on the artist and the distributor supporting it.

Why it matters for makers

The mechanism worth naming is that a listener never sees an artist's disclosure directly; it passes through a distributor's delivery pipeline first. That means the credit only exists on a platform if the distributor has built support for it, which Spotify's own page confirms is not yet universal. For a maker, the practical unit of disclosure is not a claim made anywhere convenient, such as a bio or social post, but a specific delivery-file submission that a specific distributor has agreed to carry.

What to check before you use it

This is an editorial reading beyond what either document states outright. Ask your distributor directly whether it currently supports submitting AI credits to Spotify, since capability varies by distributor. Disclose each AI-assisted role separately from human ones, as Spotify's credit model is role-based rather than track-based. Do not assume a competitor's undisclosed track is human-made; Spotify's own language warns that absence of a credit is not evidence of anything.

• Does your distributor currently support submitting AI credits into its delivery file for the platforms you release to?
• Have you separated which specific roles on a track (vocals, lyrics, production) used AI, rather than labelling the whole track?
• Would your disclosure survive being checked against the delivery file your distributor actually sends, not just your own promotional text?

Until a maker's distributor carries the field, a disclosure intention has no path to a listener; the standards work between DDEX, distributors and platforms, not the artist's own statement, is what turns that intention into something a listener can see.

Continue in Listening & research, or Spotify set new rules on AI voice clones, spam and disclosure.