If origin is unclear, rights and licensing systems cannot route value calmly across HUMAN, SEMI-MIX and AI GEN works.
ACC initiative
Join the origin standard before AI music is routed without one.
ACC is an invitation to build the neutral provenance layer for music: a declaration standard, public trust marks, ACC API and ledger architecture that can be adopted by creators, DSPs, distributors, labels and catalog owners.
Market brief
The fight is for the origin layer of AI-era music.
This is not only a certification tool. The winner defines how origin is declared, displayed, searched, routed and monetized when human and AI contribution become permanent parts of music infrastructure.
The layer that defines provenance will influence upload forms, DSP filters, catalog workflows and compliance data.
Creators need a declaration ritual that protects trust without forcing them into accusation, panic or silence.
A large ACC declaration dataset can become the reference layer for market behavior, analytics and future regulation.
A real ISRC can return music metadata while ACC returns no certification. That absence is the product opportunity.
The controlled release issues certificates, computes hashes, exposes API objects and creates OTS-ready ledger anchor proof.
Distributors, DSPs, catalog owners and licensing systems need a stable origin signal they can read and route.
ACC does not sell AI detection. It sells declaration, hash integrity, verification and market-readable status.
Scale claim
Evergreen catalogs should not be certified track by track by hand.
Ledger models how a catalog of 200,000 recordings can move through ACC in minutes under explicit throughput assumptions: metadata in, audio hashes and declarations bound, ledger events created, batch roots anchored, ACC API and public proof emitted.
Commercial logic
Push through institutions. Pull through culture.
ACC starts where pain is operational: distributors, DSPs, labels and catalog owners need a routing signal for HUMAN, SEMI-MIX and AI GEN. Public marks then create demand from creators and audiences.
Free or low-friction creator certification builds the declaration dataset and public proof layer.
DSPs, distributors, labels and catalog owners pay for verification, routing, analytics and compliance-grade access.
Bulk onboarding turns evergreen catalogues into certified, searchable and partner-readable assets.
Rights routing gap
AI music has made origin a market question, not just a legal question. Rights and licensing teams need a category for SEMI-MIX before routing, review and partner reporting become paralysis.
C2PA positioning
C2PA can carry technical provenance. ACC is the declaration and certification layer for music origin: the deed, mark, verification boundary and partner-readable status.
Commercial paths
- Catalog onboarding and bulk certification for labels and distributors.
- API verification for DSP, distributor, licensing and clearance workflows.
- Public marks for listener trust and rights-adjacent marketplace filters.
- Blockchain anchor receipts for tamper-evident provenance events.
Trust boundary
ACC does not sell an AI detector or legal authorship judgment. It sells declaration, hash integrity, public verification, revocation status and partner-readable provenance.
FAQ / Objections
The hard questions are not a threat. They are the sales process.
No. ACC is deliberately not an AI detector. ACC verifies a submitted creator declaration, timestamp, audio hash, declaration hash, certificate status and public verification URL. It gives the market a readable declaration layer instead of a black-box accusation.
A declaration is not blind trust. It creates accountability: an identified declarant, category, timestamp, hashes, public proof, status history and future revocation or dispute handling. Markets already rely on declarations; ACC makes them structured, visible and machine-readable.
C2PA can carry technical provenance and content credentials. ACC is the music-specific declaration and certification layer: HUMAN, SEMI-MIX or AI GEN, bound to an audio work, public mark, verification boundary, ledger event and ACC API response. The two can be complementary.
ACC does not make lying impossible. It makes false declarations traceable, attributable and operationally actionable. A false claim can move into disputed or revoked status, and partners can stop routing the mark as trusted proof.
Join the pilot / request the brief
Bring ACC into a real partner workflow.
For DSPs, distributors, catalog owners, labels and creator networks, start with one email. We will respond with the relevant workflow, pilot scope and validation questions.