How Audiverify documentation works in practice
Walk through a real workflow -- from certificate creation to public verification to dispute response. Everything shown here reflects the actual system.
66
Certificates Issued
2
Registered Creators
0
Public Verifications
Live data from the platform
Try It Live
These are real outputs from a real certificate on the platform. Click to explore.
The Documentation Workflow
From upload to dispute-ready evidence, in three steps.
Certificate Created
An artist uploads their WAV file and declares it as an original work. Audiverify generates a SHA-256 fingerprint and issues a timestamped certificate with a unique number.
Certificate MOT-2026-O8RZNDOO is created with full metadata, ISRC GXHE72600042, and audio fingerprint.
Public Verification
The artist shares the verification link with their distributor. Anyone with the link can confirm the certificate exists, check the timestamp, and view the declaration.
No account needed. The link is publicly accessible and shows the certificate status in real-time.
Evidence Ready
If a dispute arises, the artist downloads a Dispute Response Kit -- a ZIP containing a timeline, evidence summary, audio fingerprint data, and ready-to-paste response templates.
The kit includes machine-readable JSON data for legal teams and platform-specific response templates for content disputes.
What Partners See
When you share a verification link, this is what the recipient sees -- no account required.
Certificate Verified
This record exists and is active
Certificate
MOT-2026-O8RZNDOO
Status
ActiveTrack
C (Demo)
Artist
Sasa Radic
Registered
13 February 2026
ISRC
GXHE72600042
Audio Fingerprint (SHA-256)
a7f3d1b2c9e84f6a0b5d2e7c3f8a1d4b6e9c2f5a8d1b4e7c0f3a6d9b2e5c8f1
This is a real certificate. Verify it yourself at audiverify.com/verify/MOT-2026-O8RZNDOO
Inside the Dispute Response Kit
Every certificate can generate a downloadable ZIP with everything you need to respond to a dispute.
00-README.txt
Overview of the kit contents and how to use each file in a dispute.
01-timeline.txt
Full chronological event log -- every action on the certificate from creation to present.
02-evidence-summary.txt
Audio fingerprint (SHA-256), contributors, attachments, and version relationships.
03-response-youtube-contentid.txt
Pre-written response template for YouTube Content ID disputes, pre-filled with your certificate data.
04-response-spotify-distrokid.txt
Pre-written response for Spotify and distributor takedown disputes.
05-response-generic.txt
Generic dispute response template for any platform or legal proceeding.
06-evidence-data.json
Machine-readable JSON with all evidence data, for legal teams or automated systems.
Real Scenarios
How documentation is used in practice for release prep and dispute response.
Documenting before distribution
Before sending my album to the distributor, I documented all 12 tracks with Audiverify. Each got a unique certificate number, timestamp, and SHA-256 fingerprint. I shared the verification links in my delivery email. When a split dispute came up 3 months later, I had the timestamped record to show exactly what was declared and when.
Outcome
Timestamped documentation was available before the dispute arose.
Independent artist, 12-track album
Responding to a Content ID claim
I received a Content ID claim on YouTube for a track I wrote and produced. I downloaded my Dispute Response Kit from Audiverify, which had the pre-written YouTube template already filled in with my certificate number, registration date, and SHA-256 fingerprint. I submitted it with the verification link. The claim was resolved shortly after.
Outcome
Pre-built evidence package was submitted directly to the platform.
Producer, YouTube Content ID dispute
Ready to document your work?
Start with 2 free credits. No card required.