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.
162
Certificates Issued
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 AUD-2026-9VQFNHSY is created with full metadata and SHA-256 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.
Record Found - Active
This record exists in our registry
Certificate
AUD-2026-9VQFNHSY
Status
ActiveTrack
Jackal
Artist
Sasa Radic
Registered
3 April 2026
ISRC
GXHE726100192
Audio Fingerprint (SHA-256)
f1fe0baac428a0aeaaf48d6a497095cadd03b335646a9791fbdfd81328d57177
This is a real certificate. Verify it yourself at audiverify.com/verify/AUD-2026-9VQFNHSY
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.
Every certificate can generate this kit instantly from the dashboard.
Real Scenarios
How documentation is used in practice for release prep and dispute response.
Documenting an existing catalog
I had 40 released tracks with no documentation. I uploaded my entire back catalog to Audiverify in one afternoon. Each got a unique certificate number, timestamp, and SHA-256 fingerprint. When a split dispute came up 2 months later, I had timestamped records to reference in my response.
Outcome
Retroactive documentation was available when needed.
Independent artist, 40-track catalog
Responding to a Content ID claim
I received a Content ID claim on YouTube for a track I wrote and produced. I documented the track immediately and downloaded my Dispute Response Kit. The pre-written template was filled in with my certificate number, registration date, and SHA-256 fingerprint. I submitted it with the verification link.
Outcome
Evidence package was submitted directly to the platform.
Producer, YouTube Content ID dispute
Ready to document your work?
Complete KYC verification to receive 2 free credits. No card required.