Wav Linq is audio attribution infrastructure: embed proof of ownership into the sound itself, then detect it wherever that audio ends up. Credit follows the audio because detection — in the app or on partner platforms — recovers your Linq ID on any copy and attributes the work back to you.
Two products, one loop
Wav Linq splits into two sides that work together:
Creator Hub
Creator Hub is the creator product: the app where you embed watermarks, run extraction, and track attributions. Upload a track on the Embed page, check suspect files on Extract, and watch matches roll into your Attributions feed and dashboard. No API key required.
Platform API
Platform API is the integration layer for platforms, distributors, labels, and developers. Partners wire the Detection and Embed APIs into their pipelines — each integration becomes a node in the Wav Linq network, scanning audio as it moves and resolving attribution at scale. That's universal detection: your work gets credited wherever a node is listening, without you uploading files to each platform.
Creator Hub is where creators establish proof. The Platform API is how that proof gets found across the open web.
How it works
- Embed — Write an imperceptible Linq ID into your audio in Creator Hub.
- Share — That audio moves through exports, MP3s, social clips, and platform uploads.
- Extract — Verify a copy yourself in Creator Hub, or let a partner node scan it through the Platform API.
- Detection — When a node finds your Linq ID, attribution resolves to you and surfaces in Creator Hub.
Embed once. The network handles the rest.
Key terms
Linq — The imperceptible watermark in the audio signal.
Linq ID — The unique signature in that watermark, tied to your account and that audio. Detection resolves it to attribution data.
Embed / Extract — Writing a Linq ID into audio, and reading it back out. Same engine in Creator Hub (the app) and Platform API (the integration layer).
Attribution — The credit chain from a piece of audio back to its creator or rightsholder. Proactive proof at embed time; detection fulfills the promise that credit follows the audio.
Attribution lives in the signal, not the file wrapper. ID3 tags break on re-encode and re-upload. A Linq ID survives compression, sample-rate changes, and platform processing.
Where to go next
Creators → Intro to Creator Hub
Platforms, labels, and developers → Intro to Platform API
- Product Overview — technical concepts and survivability
Ready to try it? Create a free account and embed your first Linq ID in minutes.