Music origin / AI era / verifiable trust

The trust mark for music origin.

ACC turns a creator declaration into a visible market signal: HUMAN, SEMI-MIX or AI GEN, bound to the audio file, sealed by hashes and exposed through the ACC API.

Certify a track Verify the mark

ACC / ISSUEDACC-2026-023F0159

Certified provenance classHUMAN

Audio hash and declaration hash recorded.

SEMI-MIX

HUMAN

AI GEN

Origin markA visible label listeners and partners can recognize.

Public proofA certificate page tied to hashes, declaration and status.

API signalA provenance object that distribution systems can read.

ACC initiative

Help set the origin standard before AI music sets it by accident.

ACC is looking for pilot conversations with DSPs, distributors, catalog owners, labels and creator networks that need a practical origin signal before AI-era repertoire becomes operational noise.

Request partner pilot Run partner walkthrough Open verification

Architecture of Trust

AI did not only create more music. It broke the old instinct for origin.

The market needs a standard that is calmer than accusation and stronger than metadata. ACC gives creators a declaration ritual, partners a readable object and audiences a mark they can recognize.

When origin matters, trust has to be rebuilt.

Moment of transformation

A track enters as a file. It leaves as a verified market signal.

Before ACCaudio.wav

Origin unclear. AI disclosure unavailable. No public verification.

Name the work

Title, artist, phonogram producer and ISRC create the market identity.

Bind the audio

The file receives a SHA-256 hash at submission.

Declare origin

The creator selects HUMAN, SEMI-MIX or AI GEN under the ACC creator declaration.

Issue proof

The certificate becomes visible to listeners and readable to partners.

After ACC

HUMAN

Public certificate, hashes, declaration and API-readable verification.

Market desire

The badge belongs where listening decisions happen.

ACC becomes valuable when it travels with the work: in catalogues, platform filters, licensing flows and public verification moments. That is where a certificate becomes a cultural signal.

Origin modeOnly HUMAN

Now playingAfter the Machine Rain

Mira Vale

After the Machine RainMira Vale

Verified origin

HUMAN

Glass PromptsNora Syn

Declared mixed authorship

SEMI-MIX

Synthetic DawnAster Model

Open synthetic disclosure

AI GEN

The marks

Three labels. No moral panic. No black-box accusation.

HUMAN

For music whose value depends on human authorship, craft and trust.

A premium mark of origin.

SEMI-MIX

For works where human direction, input and AI systems both shape the outcome.

The missing category for mixed authorship.

AI GEN

For openly AI generated music that deserves transparent market access.

A clear signal for the new frontier.

Operational proof

The mark is emotional. The proof is operational.

ACC issues a certificate, computes an audio hash, records the declaration, exposes JSON responses and opens a public verification page. It is not a slide. It is a working certification surface.

Open the product

ACC API

A certificate mark that machines can read.

For distributors, DSPs, labels and clearance teams, ACC becomes a stable data object: category, status, hashes, declaration version, anchor batch status and public verification URL.

AI music disclosure APImusic provenance certificatemusic rights clearance APIverify AI generated music declaration

GET /api/v1/certificates/ACC-2026-023F0159

{
  "certificateId": "ACC-2026-023F0159",
  "status": "pending_anchor",
  "category": "SEMI_MIX",
  "work": {
    "title": "After the Machine Rain",
    "artistName": "Mira Nowak",
    "declaredProducerName": "Mira Nowak",
    "isrc": "PL2O52600001",
    "isrcDisplay": "PL-2O5-26-00001",
    "isrcSource": "acc_assigned",
    "isrcAssignedBy": {
      "name": "Art Clearance Certification Sp. z o.o."
    }
  },
  "audioHash": "2ee3c35b4d2af17f0d0f...",
  "declarationVersion": "acc-declaration-standard",
  "anchorBatch": {
    "batchId": "ANCHOR-2026-486BF412",
    "status": "submitted",
    "blockchain": "OpenTimestamps-ready / Bitcoin pending"
  },
  "verificationUrl": "https://verify.artclearancecertification.org/ACC-2026-023F0159",
  "accVerificationBoundary": "ACC verifies declaration submission, timestamp, audio hash, declaration hash and certificate status. ACC does not independently detect AI."
}

Partner workflows

How the market uses ACC.

The walkthrough is organized around partner workflows, not internal modules: issue proof, read status, certify catalog scale and verify the public signal.

Creator / label intakeIssue proof at submission

Bind an audio file, declarant identity level and origin declaration into a public ACC certificate.

Distributor / DSPRead origin in workflow

Query certificate status, ISRC, hashes and verification URL before routing catalog decisions.

Catalog ownerCertify at catalog scale

Model how large evergreen catalogs move through batches, ledger events and OTS-ready anchors.

Rights team / public proofVerify the market signal

Open the same proof object that partners, rights teams and listeners can inspect.

Trust boundary

ACC is not an AI detector. That is the point.

ACC verifies declaration submission, timestamp, audio hash, declaration hash and certificate status. It does not replace copyright analysis and it does not pretend to know what no machine can reliably know.

It creates a standard declaration layer that markets, rights systems and listeners can act on.

Pilot path

Bring one real workflow. ACC will show the proof path.

The controlled release issues certificates, computes hashes, exposes public verification, returns ACC API objects and models ledger anchoring. A partner pilot tests where that signal reduces friction inside a real upload, catalog, licensing or distribution workflow.

Request partner pilot Send pilot request