Catalog flooding becomes an operating cost
AI-era volume does not only create more music. It creates more review, more edge cases, more metadata ambiguity and more pressure on recommendation, moderation and catalog teams.
Partner brief / DSP-ready BETA
ACC turns music origin into a status your systems can read.
For DSPs, distributors and catalog owners, the painful question is not philosophical. It is operational: how do we route, label, review and trust AI-era catalog at scale without relying on accusation or incomplete metadata?
Metadata exists, origin proof does not
A DSP or distributor can often identify a recording through ISRC metadata, while still having no structured answer to whether the work carries a declared origin status.
AI detection is not enough
Black-box detection creates accusation risk. ACC gives partners a declaration, hash, public certificate, status and API object that can be routed without pretending to be a magic detector.
3-minute partner demo
What a DSP or distributor should see first.
Issue one certificate
Open Creator and generate a sample ACC certificate from a test audio file, identity level and declaration.
Open public proof
Check the mark, status, hashes, declaration version and verification boundary.
Read ACC API
See the same certificate as JSON for ingestion, routing, audit and partner reporting.
Search a real ISRC gap
Search a known external ISRC and see metadata found while ACC returns NOT_CERTIFIED.
Model catalog scale
Open Ledger and model batch certification, ledger events and OTS-ready anchor proof.
What the pilot tests
ACC should be tested where the pain is already real: catalog intake, metadata quality, AI-era disclosure, public trust UX, rights review and API-readable routing.
What ACC returns
- A small workflow map: where origin data enters and where ACC status is consumed.
- Sample certificates and public verification URLs.
- ACC API response examples for certified and not_certified works.
- Ledger / anchor evidence for batch integrity.
- A written fit-gap note after the 30-day pilot.
Pilot request
Bring one painful workflow.
The first pilot does not need a huge integration. It needs one real workflow, one owner of the pain and a small dataset that shows whether ACC creates a useful market signal.