Product overview
How Wav Linq works.
Linq ID
The identity embedded in your audio
A 20-character composite signature — 12 characters tied to your creator account, 8 tied to the specific track. Lightweight, inaudible, and impossible to strip without destroying the audio. Even if the song-level portion is damaged, the creator portion survives.
Embedding
Written into the signal, not the wrapper
Wav Linq uses frequency-domain amplitude modulation — the Linq ID is encoded into the audio signal itself, not metadata tags. Parameters are optimized per file based on audio characteristics. The result is inaudible to listeners and survives compression, re-encoding, and platform processing.
Detection
Attribution on any copy of the audio
Detection extracts the Linq ID from audio and resolves it against the registry. For federated partners, resolution calls your own HTTPS endpoint — your metadata never leaves your database. Results include the creator, the track, and an
attribution_source indicating how the data was retrieved.
Wav Linq API
Built for platform integration.
Both APIs use the same DB-backed key system. See the integration guide and API status to get started.
Detection API
Async watermark detection via job polling
Submit audio, receive a
job_id, poll until succeeded. Designed for platform-scale integration — rate-limited, idempotency-keyed, auth-gated. Federated resolution means partner metadata stays in your own database.
Embed API
Batch watermarking for catalogs
POST audio and a resolver URL, receive a watermarked WAV and the embedded Linq ID in response headers. Ideal for distributors, labels, and platforms watermarking at scale. Supports full federated embed — Wav Linq stores only a routing pointer, not your metadata.
Watermark survivability
| Transformation | Result |
|---|---|
| Compression | |
| 320 kbps MP3 | High |
| 192 kbps MP3 | High |
| 128 kbps MP3 | High |
| 96 kbps MP3 | High |
| Sample rate conversion | |
| 48 kHz | High |
| 44.1 kHz | High |
| 32 kHz | High |