CD Baby's two AI documents do not say the same thing

The tool moment

CD Baby, a music distributor owned by Downtown Music, publishes its content rules across more than one current help page, and the two most relevant ones do not draw an identical line on artificial intelligence. The company-wide content policy, dated October 2025 on the page itself, applies across Downtown Music's services, including CD Baby, FUGA, and Downtown Artist and Label Services, and prohibits content 'created wholly or primarily by AI models trained on copyright protected sound recordings without a license,' plus AI-generated content that mimics a named artist. A separate help article, on what CD Baby calls Production Sounds, non-music audio such as white noise, ambient recordings, and ASMR, states a flatter rule for that category: 'No. We cannot accept any AI-generated content, even if it's commercially licensed.'

What the documents show

Read side by side, the two documents describe different scopes rather than a single contradiction. The company-wide policy is conditional: it targets unlicensed AI training data and artist-mimicking content, which leaves room for licensed, disclosed AI-assisted work elsewhere in CD Baby's catalog. The Production Sounds article states an unconditional rule specifically for that non-music category, rejecting any AI-generated content in it regardless of licensing, and warns that repeated attempts to deliver it may end the relationship with the account. Neither page states that its own rule applies to every kind of release CD Baby distributes; a producer has to read the page that actually matches their content type rather than assuming one CD Baby AI policy covers everything.

What stays with the musician

Because CD Baby's guidance is split across documents with different scopes, an artist cannot rely on having read one AI policy page and assume it covers a different kind of release. Someone delivering a conventional song with AI-assisted mixing needs the company-wide licensing standard; someone delivering an ambient or noise track built with AI tools needs the stricter Production Sounds rule instead. Confirming which document actually governs a given release, and keeping licensing documentation for any AI tool involved, remains work the artist has to do before delivery, not something either page resolves generically.

Judge it by listening

Neither document proposes a listening method; both are rules about permission and category, not audio quality. Editorially, the useful check here is procedural rather than auditory: before delivering a release, an artist should identify which category it falls into under CD Baby's own pages, non-music Production Sounds or standard music content, since that determination changes which of the two documented rules actually applies to the track.

• Does this release count as music, or as Production Sounds under CD Baby's own category definitions?
• Can I document a license for any copyrighted material the AI tool I used was trained on?
• Have I checked the specific help page that matches this release, rather than assuming one CD Baby AI policy covers every kind of content?

CD Baby's guidance shows why a musician has to check a distributor's current pages for the specific release type at hand, rather than treating 'the AI policy' as a single fixed rule.