Suede DistroSpotify AI Credits
Spotify describes an optional, mobile-only beta using role-level credits supplied through participating distributors. Missing credits do not prove that a track used no AI.
Read Spotify’s AI Credits guideAI release readiness · Wave 2
The AI music rush needs receipts.
Platforms are adding more ways to describe AI contributions and protect artist profiles. Build a role-level release record, catch unresolved rights questions, and map the money paths before a store or collaborator asks.
What changed—and what did not.
Artist Profile Protection
Spotify describes an optional limited beta where eligible artists can review releases from most providers before profile attribution. Suede does not ask for the confidential artist key.
Read Spotify’s protection guideArticle 50 transparency
Article 50 duties generally apply from August 2, 2026 to specified AI providers and deployers. A limited transition lets providers of systems placed on the market before that date meet Article 50(2)'s marking and detection duty by December 2, 2026. Other duties, exceptions, and the legal role depend on what a business provides, deploys, and controls; this planner does not decide them.
Read Article 50Read the Commission timing FAQEuropean Commission guidance explains how these transparency duties are interpreted for providers and deployers. Read the Commission guidelines.
Local-only workbench · no account required
Build the release record.
Building or exporting the packet does not upload it. If you separately join Wave 2, the current AI-use category is copied into that submission with the email, selected first royalty path, and consent record. Hosting, security, rate-limit, and email providers process limited operational data described in the privacy notice.
One release. More than one money path.
Spotify explains that recording royalties normally reach the rightsholder through a label or distributor, while publishing royalties follow separate systems. The map below is a setup checklist—not a promise that every lane applies to every release.
Spotify royalties guidePATH 01
Master recording
Distributor or label
Streaming and download recording revenue normally flows from the service to the rightsholder through its distributor or label.
PATH 02
Performance royalties
PRO or CMO
Songwriters and publishers register compositions with the relevant performance-rights organization or collective-management organization.
PATH 03
U.S. digital mechanicals
The MLC or a publisher/admin
Eligible self-administered songwriters and publishers can register works with The MLC for U.S. blanket digital mechanical royalties.
PATH 04
Neighboring rights
SoundExchange or territorial CMO
Non-interactive digital performance and neighboring-rights paths depend on the recording, territory, service, and claimant role.
PATH 05
Collaborator splits
Signed split sheet, then each service
Agree master and composition shares before delivery. A distributor split tool does not replace the underlying collaborator agreement.
PATH 06
UGC and sync
Eligible provider or licensing representative
Content ID, social-video monetization, and sync each have separate eligibility, rights, fee, and representation questions.
The U.S. mechanical lane
The U.S. Copyright Office says The MLC administers the blanket license for eligible digital uses and invites songwriters and publishers to register so they can receive royalties.
Suede does not currently collect, split, route, or settle royalties.
The packet follows the language taking shape.
DDEX ERN 4.3.2 includes fields named ContainsAI and AiContribution. Suede uses a simpler local preparation record inspired by those concepts. It is not a DDEX message, a licensed DDEX implementation, or proof that a distributor or DSP ingests it.