ACC / music origin

Creator workflow: issue proof

For CreatorsMy Certificates
0Issued
0SEMI-MIX
0API checks

Creator

Music work intake

Put a serious origin mark on your music. ACC hashes the audio in your browser, records your creator declaration and returns a public certificate, mark, QR, PDF and partner-readable API object.

1. AudioHash locally. ACC does not store the audio.
2. IdentityChoose Level 1 email or Level 2 signed evidence.
3. DeclareSelect HUMAN, SEMI-MIX or AI GEN.
4. ProofIssue the certificate and open public verification.
No audio upload to ACCThe browser calculates SHA-256 locally. ACC stores the hash and declaration data.
Creator account previewAfter issuing, your certificate appears in My Certificates with the full download pack.
ISRCInternational Standard Recording Code: stable identifier used by music catalogues and distribution systems.Existing ISRC

Audio fileACC can use a real uploaded file or generate a short WAV for reference during validation.

No file selectedUpload audio or generate a reference WAV
Audio hash pending
ClassificationHUMAN

ACC declarationA recorded creator statement about HUMAN, SEMI-MIX or AI GEN origin. ACC verifies the submission boundary, not independent authorship.

I declare that the material creative expression of the work was created by human author(s), and that generative AI did not produce material creative output claimed as part of the work.

HUMAN declaration ritualThis work is mine. Human-made.

I am placing a public origin mark on this music and I understand that the declaration is recorded.

Typed signature and acceptance are recorded in the declaration payload.

Declarant verificationACC records how strongly the declarant identity is bound to this declaration.

Level 1

Certificate

No certificate selected