DISTROBOLT

DISTROBOLT ARTIST GUIDES

AI music and Content ID: check eligibility before you select it

AI-assisted or generated music needs a separate Content ID eligibility check. Acceptance for ordinary catalogue distribution does not establish exclusive rights or permission to activate an automated matching service.

Map what the reference contains

Record human performances, generated audio, licensed beats, loops, samples and any cloned voice. Keep the relevant tool terms and source permissions with the exact final master. A statement that you can commercialise an output does not necessarily answer whether every matching passage is controlled exclusively.

Read the matching-service requirement

YouTube requires exclusive rights for eligible Content ID reference material in the territories claimed and identifies exclusions for non-exclusive third-party content. Apply the current rule to the actual sources rather than assuming an AI label decides the answer. Do not upload an ineligible reference simply to discover whether it triggers claims.

Confirm the distributor’s supported route

Ask DistroBolt and the applicable delivery partner about AI-specific matching restrictions, evidence and available destinations. Keep the written answer dated and model-specific where relevant. This guide does not certify WBBT support or a universal ban on every AI-assisted recording; unresolved eligibility stays unresolved.

Separate claims from distribution

A delivery to YouTube Music and activation of Content ID are different actions. Keep that distinction in the release plan and avoid competing reference submissions through several providers. If an incorrect claim occurs, preserve the affected links and source evidence and use the supported review route rather than changing royalty splits.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

Continue your release planning

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.