AI platforms decline music requests they cannot verify. A Rights Cleared credential makes your music license independently queryable so licensed requests can complete.
Join →Select your rights holder, the type of rights, territory, and term — start and end date. No agreement text is submitted or required. Rights.dev never sees your agreement.
Rights.dev issues a signed Rights Cleared credential. You carry a license ID tied to that credential — one per licensing relationship.
AI platforms query Rights.dev with your license ID. Verification returns in milliseconds and the request is served.
Some organizations both own rights and hold licenses from other rights holders. If that is your model, start on the rights holder path — you will register your own licensing relationships and receive credentials for the licenses you hold from others.
If you hold licenses only — from labels, music publishers, or other rights holders — start here.
Not sure which applies? →A Rights Cleared credential is a signed, machine-queryable record confirming that you hold a valid license from a rights holder. AI platforms query Rights.dev with your license ID and receive a verification response in milliseconds — without needing to contact your rights holder directly.
Yes, but the work is minimal on their side. You initiate the process: register the licensing relationship by selecting your rights holder, the type of rights, the territory, and the term. Your rights holder then receives a confirmation request and simply verifies that your registration is accurate. Once they confirm, your Rights Cleared credential is issued automatically. No new agreement is required on either side.
Yes — one credential per licensing relationship. Each credential carries its own license ID reflecting the specific rights, territories, and term granted by that rights holder. All credentials are queryable through the same Rights.dev API.
When your license expires, you update the registration and your rights holder confirms the change — or your rights holder may revise or revoke the credential directly. When your license is renewed, you update the registration and your rights holder confirms the new term. The credential reflects the change in real time. AI platforms always query the current state.
No. The credential confirms that a licensing relationship exists, for what rights and territories, and through what dates. Royalty rates, advance amounts, and deal structure are never accessed or stored. License terms remain entirely in your agreement with your rights holder.
Query logs are accessible to the rights holder who confirmed your license. As the licensee, your access to query data depends on the terms agreed with your rights holder. This is something to establish as part of your participation in Rights.dev.
Start on the rights holder path. You will register the licensing relationships you grant to others and receive credentials for the licenses you hold. Rights.dev handles both directions for organizations that operate in both capacities.
If you hold a license from a music rights holder and need AI platforms to verify that license before serving your content, this applies to you. That includes licensed music retailers, streaming platforms, sync libraries, sheet music distributors, karaoke services, and AI music tools operating under a music license.