AI assistants now represent significant demand for licensed music — across compositions, recordings, and licensed editions. They cannot verify who is authorized to supply it. Rights.dev verifies those licensing relationships so that licensed demand can be served.
Join →Existing registries — MLC, HFA, CISAC, and others — record who owns rights. They do not record who is licensed to supply them, for what rights, in which territories, or through what dates. That is what AI platforms need before they can serve a request, and it does not exist in a machine-queryable form today.
Rights.dev is that layer. Your licensees register the relationship — selecting the type of rights, territory, and term. You confirm. A signed Rights Cleared credential is issued as a certificate. AI platforms query it in milliseconds.
Rights.dev never sees your agreement. Only four data points are recorded: rights holder, type of rights, territory, and term.
Your licensee registers the relationship — selecting the type of rights, territory, and term (start and end date). Your role is to confirm that the registration is accurate. You are not providing new information; you are verifying what your licensee submitted.
When a license expires or is amended, the licensee updates the registration and you confirm the change. You may also revise or revoke a credential directly at any time — the change takes effect in real time.
Every verification query is logged. The log data belongs to you — you see which AI platforms queried for your content, and when. That record is available for royalty calculation, reporting, and negotiations.
Rights.dev does not share your query data with other rights holders or licensees.
Founding membership is not a pilot program. It is a governance position that shapes the standard for its lifespan.
Permanent seat on the body that sets credential schema, audit standards, and revocation protocol. Founding seats are not transferable. Standards shaped by those at the table now determine how AI platforms integrate against Rights.dev.
Every verification query against your content is logged and timestamped. You see which AI platforms queried, and when — a documented basis for royalty claims in AI channels. Rights.dev does not share your query data with other rights holders or licensees.
Revise or revoke any credential directly at any time, without waiting for the licensee. Changes take effect immediately across every AI platform querying Rights.dev. You are never locked into a credential you no longer stand behind.
Governance belongs collectively to founding members. Credential schema, audit standards, and revocation protocol require collective agreement.
Read governance →Those registries document who owns copyrights. Rights.dev records the next layer: who you have licensed, for what rights, in which territories, and through what dates. That is the specific information AI platforms need before serving a request, and it does not currently exist in a machine-queryable form.
Your licensee does the registration — they select the type of rights, territory, and term (start and end date). You receive a confirmation request and verify that the information is accurate. That is all. No new agreement, no per-work approvals, no data entry on your side.
When a license expires or is amended, the licensee updates the registration and you confirm the change. You may also revise or revoke a credential directly at any time without waiting for the licensee — the change takes effect in real time. AI platforms receive the updated state on their next query.
The query log data belongs to you. You have access to your own logs — which AI platforms queried for your content and when. Rights.dev does not share your data with other rights holders or licensees.
No. Rights.dev references relationships only — who is licensed, for what rights, in which territories, and through what term. License terms, royalty rates, and deal structure remain in your agreements and are never accessed or stored.
Rights.dev is independently operated. Governance authority — over credential schema, audit standards, and revocation protocol — belongs collectively to founding rights holders. No single organization controls the standard.
Rights.dev is pre-launch. The specification and credential schema are being defined now. Founding rights holders shape the standard that AI platforms will integrate against. The earlier you participate, the more the standard reflects your requirements.
The credential schema and verification protocol are open standards, governed collectively. No single operator controls them. The standard is designed to outlast any individual operator.