From catalog lookup to approval

The released v0.1.0-alpha.1 uses AGPL-3.0-only. The proposed Own-Node and Partner Licenses apply to a future source-available release once adopted. Earlier grants and component licenses continue to apply.

Yes. The proposed Own-Node License permits an organization’s own rights administration, including catalogs it genuinely represents. Revenue from administering and licensing those rights is within that scope. The released alpha follows its AGPL terms.

Your employees can self-install and use coding assistants. Clef can provide setup under a services agreement. An outside installer or maintenance provider needs a separate Clef Partner License covering your organization.

Offer setup, catalog imports, branding, integrations, staff training and ongoing maintenance. You set your service prices and retain that service revenue. Clef provides the software and shared technical documentation. US$1,200 per client organization, billed annually. Each partner’s first client receives a first-year price of US$600; renewals and additional clients are US$1,200 annually. Activation fee: US$0. Applicable taxes are additional. The proposed standard partner license authorizes these services for registered client organizations.

The standard program covers installation and support in the client organization’s infrastructure. The client controls its catalog data, access and licensing decisions. Partner-hosted services, OEM distribution and other resale require a separately scoped agreement.

You provide day-to-day customer support. Clef provides shared documentation and software issue channels; bespoke assistance is scoped separately. If a partner stops renewing, its commercial service entitlement ends. The client keeps its applicable own-node rights, records and exports and can self-administer or select another licensed partner.

The partner first-client offer is separate from the 50% discount on Clef-assisted pilot setup fees. The partner offer reduces one annual partner license; the Clef-assisted offer reduces the agreed setup service fee.

The form records interest and delivers the proposed offer. Activation follows a completed agreement, eligibility checks and the designated software release.

The label or publisher identifies the right, controlled share, territory and supporting agreement. A node operator reviews that evidence. Authority records distinguish self-asserted, verified, disputed, rejected and revoked claims. Each permission has its own term, decision and history of later corrections, disputes or revocation.

Authorized lookups from The MLC help identify musical works and review publishing claims in its U.S. administrative context. Recording metadata is supplied to The MLC by DSPs and processed as received. The label or other recording rightsholder supplies evidence of master ownership and controlled shares; publishers supply their mandates and territorial scope. Your reviewers use those records to decide each requested permission.

The alpha validates Musical Work Licensing (MWL) files against specified DDEX schemas and records exchange evidence. Production transport, counterparty conformance, and legal effect require a bilateral operating arrangement.

The administrator can require exact text, URL, placement, metadata, and reporting in the signed grant. A requester reports publication, an administrator records compliance evidence, and any dispute or revocation remains a separate signed action.

Clef records externally calculated royalties, payment evidence, beneficiary payouts, reversals, and reconciliation. A regulated provider remains responsible for money movement and related duties.

Yes. The same workflow supports other music uses through catalog policies, evidence review, approval records, and reporting.