The 60-second AI release decision matrix

Start with what you actually made. The same “AI song” label can describe radically different rights and platform situations.

The five gates between your AI track and a sustainable release

The order matters. A creator who starts at Gate 2—“Will DistroKid take this?”—can miss the harder Gate 1 question about rights and the completely separate Gate 5 question about exclusivity.

Suno, your distributor, Spotify and Content ID are different rule systems

The generator answers whether its terms give you commercial permission. The distributor decides whether it will deliver the release. The streaming service decides how it hosts, classifies, recommends and enforces the content. A fingerprinting or UGC system can then make another eligibility decision based on exclusive-rights requirements.

That is why “Suno says I can monetize it” and “YouTube Content ID should accept it” are not interchangeable statements.

Fully generated, partly generated and AI-assisted are not the same

Distributor decision matrix for AI music creators

This is the practical difference between a distributor list and a release decision. A service can accept AI music while imposing destination, timing or UGC restrictions that matter more than its headline price.

Which distributor should you use?

DistroKid: AI music is accepted, but the uploader carries the rights burden

DistroKid says music created with AI tools can be uploaded when the creator owns the necessary rights, does not impersonate another person's voice or identity without permission, avoids mass-generated spam and does not infringe third-party rights.

AI Credits turn “AI or not?” into a contribution record

DistroKid's AI Credits workflow asks creators to identify whether AI contributed to lyrics, music, all of the audio or part of the audio. Its guidance also distinguishes generative contribution from production assistance: ordinary pitch correction, AI mixing/mastering and similar assisted workflows do not automatically require the same generative credits.

What DistroKid acceptance does not prove

• That every element is copyrightable.
• That the recording is exclusive enough for Content ID.
• That a cloned voice was authorized.
• That Spotify, Deezer or another DSP will recommend it.
• That the release can never be removed later.

RouteNote: still a true-free option, but timing and AI destination limits matter

RouteNote remains attractive because a creator can distribute without paying an upfront subscription. Under its Free model, RouteNote keeps a percentage of revenue rather than charging the initial distribution fee.

For AI-generated releases, however, creators need to pay attention to destination eligibility. RouteNote's current support guidance explains that Content Recognition stores can be unavailable during moderation while eligibility is assessed and can be removed when a release does not qualify. Its AI-release guidance also identifies restrictions affecting AI-generated material and certain partner stores.

Best fit today: a creator who values a true-free path more than a near-term fixed release date.

ONErpm: AI disclosure is becoming more granular

ONErpm has introduced an AI self-declaration system designed to classify how AI was involved in a release. Its published explanation frames the system around transparency rather than an automatic penalty and says that, at present, tracks remain eligible for monetization regardless of AI involvement under that classification process.

The important industry signal is larger than ONErpm itself:

That is the direction creators should prepare for now. Keep records at the contribution level: lyrics, composition, vocals, instrumental generation, editing, mastering and human performance.

UnitedMasters and Amuse: “accepts AI” does not mean identical downstream rights

BandLab, LANDR and Ditto: three additional distribution lanes worth separating

CD Baby: AI-generated content is not accepted

CD Baby’s current Help Center says it cannot accept AI-generated content for distribution even when the material is commercially licensed. Its rule is broader than a ban on fully generated songs: CD Baby says a recording is still ineligible when only part of the recording is AI-generated.

Spotify: responsible AI use is different from impersonation, spam and fake streams

Spotify's current AI policy distinguishes legitimate AI use from misuse. It targets unauthorized voice impersonation, deceptive artist identity, music spam and artificial streaming rather than declaring AI-generated music itself forbidden.

Apple Music: material-AI transparency metadata is now part of delivery

Apple Music should not be described as having a blanket ban on AI-generated music. Apple’s current provider specification adds an AI Transparency metadata system for content where artificial intelligence generated a material portion of what is delivered.

Apple does not publish a universal percentage threshold for “material portion.” Do not invent one, and do not force a one-to-one mapping between Apple’s metadata and JR’s AI-Generated, AI-Assisted or Full Copyright framework. JR’s labels help describe the creator process; Apple’s values are provider/delivery metadata.

Most independent artists will encounter this through a distributor, label or delivery provider rather than by editing Apple’s delivery XML themselves. DistroKid, for example, currently asks creators for AI Credits and says supported AI-credit information is displayed by Apple Music. The creator’s responsibility is to answer those fields accurately; the distributor’s job is to translate and deliver the metadata Apple accepts.

Apple separately says it uses proprietary detection models to identify AI-platform-generated content for stream-manipulation enforcement. When Apple detects that the majority of plays for an AI-platform-generated song are manipulated, Apple says it automatically removes the song from the platform after suspected manipulation is reviewed by a human.

TIDAL: provenance, AI labels and creator proof are part of the release question

TIDAL belongs in this matrix because platform treatment is no longer only about whether a track can be delivered. The platform-specific question also includes how AI involvement, credits, provenance and listener-facing transparency are represented after delivery.

Deezer shows why detection, labelling, discovery and removal must be separated

Deezer currently provides the clearest example of platform-level treatment that goes beyond ordinary store delivery. In July 2026, it reported that fully AI-generated music had exceeded half of daily uploads at a June peak, with a monthly average around 90,000 fully AI-generated tracks arriving per day.

Beatport: AI-generated music is not accepted; AI-assisted production is a boundary question

Beatport's current Content Policy explicitly lists AI-generated music among the content it does not want. Its Terms add an important nuance: Beatport recognizes that some tools marketed as AI can function more like traditional production software or the natural evolution of music technology. Beatport has not published a percentage threshold that tells creators exactly when a hybrid release crosses that line.

YouTube Music delivery, AI disclosure and Content ID are three different systems

1. YouTube Music delivery

Your distributor can deliver a recording to YouTube Music like another DSP. That says nothing by itself about Content ID.

2. Creator and partner AI disclosure

YouTube requires disclosure of meaningfully altered or synthetic content in relevant cases and explicitly includes synthetically generated music in its examples. For music partners, YouTube supports generative-AI metadata such as Fully GenAI, Partly GenAI and No GenAI. Its examples distinguish a whole text-prompt-generated track from hybrid human/AI audio and from AI-assisted processes such as mastering.

3. Content ID

Content ID is a separate rights system. YouTube says reference material must meet exclusive-rights requirements; non-exclusive material and some commonly reused or insufficiently distinct material may not qualify.

YouTube also says disclosure itself does not automatically limit a video's audience or monetization eligibility. The disclosure requirement and the rights-claiming system solve different problems.

TikTok and Meta: library delivery, post disclosure and UGC monetization are separate

A distributor can deliver a recording to a social music library. Separately, the platform may apply synthetic-media and identity rules to creator posts. Separately again, a distributor or rights service may decide whether the recording is eligible for UGC fingerprinting or monetization.

UnitedMasters, Amuse and RouteNote all provide examples of why this distinction matters: a release can be distributable while AI-generated material remains ineligible or restricted for particular social UGC or content-recognition products.

Master rules matrix: distributor, DSP or rights system?

“Can I release this?” Eight real-world AI music scenarios

The five rights layers to check before distribution

Distribution should not become a second full rights course. Use these five layers as the handoff: if one is unresolved for the intended use, stop the upload decision and move into the JR rights system.

A compliant AI song can still be destroyed by fraudulent promotion

Creation compliance does not protect a release from streaming-fraud enforcement. The problem is not whether the listener is hearing AI. The problem is whether the listener is real.

• Do not buy guaranteed streams.
• Do not use looping farms or automated devices.
• Do not pay for unexplained fixed playlist counts.
• Do not generate fake accounts or artificial engagement.
• Do not manufacture activity to avoid an inactivity rule.

Pay for legitimate reach, creative production, advertising, publicity or audience development—not guaranteed plays.

Jack Righteous AI release-readiness scorecard 2.0

Score each area from 0 to 2. This is a planning framework—not legal advice and not a platform approval system.

• 0–7: Do not distribute yet.
• 8–12: Repair the release package.
• 13–16: Potentially viable after targeted checks.
• 17–20: Stronger operational readiness.

Build your creator record before a dispute—not after one

From generated file to platform-ready release: the JR workflow

Frequently asked questions

Choose the distributor only after the release passes the rights and readiness checks.

Use this page to compare distributor and platform rules. If you are still deciding whether the track is ready, use the Release Router first. If the route is clear and you are preparing the actual release, continue into the full AI Music Release Path.

When distributor rules become an active release problem

Use this comparison while the job is choosing a distributor. If rights, metadata, proof, platform rules and multiple release decisions now need continuity, Complete Access is the strongest JR support level. Creator Pro is the lighter option for one active release lane.