Intro to Creator Hub

Creator Hub is the creator side of Wav Linq — the app, dashboards, and workflows built for musicians, producers, podcasters, and anyone who wants ownership proof baked into their audio before it leaves their hands.

You don't need an API key or a developer account to use Creator Hub. Upload a track, embed a Linq ID, and let detection — in the app or on partner nodes running the Platform API — carry attribution wherever your work ends up.

What is Creator Hub?

Wav Linq splits into two sides. Creator Hub is where creators live: embedding tracks, checking copies, and watching attributions roll in. Platform API is what platforms and partners integrate — each one a node in the network that makes universal detection possible across the open web.

As a creator in Creator Hub, you get the full loop without writing code:

Embed a Linq ID into your audio
Share that audio however you normally would
Extract the audio yourself when you need to verify ownership
Receive attributions automatically when integrated nodes detect your watermark in the wild

Embedding puts identity in the signal. Detection — whether you run it or a partner node does — is what fulfills the promise that credit follows the audio.

Creator Hub workflows

Embed

The Embed page is where attribution starts. Upload a track, and Wav Linq analyzes the audio and writes an imperceptible watermark into the signal. You download a watermarked version with a unique Linq ID tied to your creator account and that specific track.

Do this before you send stems to collaborators, post clips, or distribute a release. One embed establishes proof at export time — not after a dispute.

Extract

The Extract page is the manual detection path. Upload any copy of your audio — a re-encoded MP3, a social clip, a download from somewhere else — and Wav Linq searches the signal for an embedded Linq ID. When a match is found, you get attribution tied back to the original embed.

Use extract when you want to check a specific file yourself. You don't have to wait for a partner platform to detect it.

Attributions

Your Attributions feed is where detection results surface over time. When a Linq ID linked to your account is found by you in the app, or automatically through a platform node integrated with the Platform API — the match shows up here with context: which track, where it was detected, and when.

This is the payoff for embedding early. You establish proof once; attributions accumulate as your audio moves.

Your dashboard

The Creator Hub dashboard is your home base. Recent watermarking activity, attribution stats, and account-level overview. Everything in one place once you're embedding and tracking a catalog.

Think of it as the command center for your Linq IDs: what you've embedded, what's been detected, and how your work is traveling.

How Creator Hub connects to the Platform API

You never interact with the Detection API directly as a creator. But every platform that integrates the Platform API becomes a node — an extension of Creator Hub's detection reach.

When a distributor, social app, or streaming service scans audio through its node, successful matches resolve back to your Linq ID and surface in your Attributions feed and dashboard. That's universal detection from the creator's perspective: your work gets credited wherever integrated nodes find it, without you uploading files to each one.

Creator Hub is the experience. Platform API is the infrastructure underneath. Together, they close the loop — embed once, attributed everywhere detection runs.

Who is Creator Hub for?

Independent musicians and producers embedding tracks before release.

Podcasters and voice creators who want persistent credit.

Anyone who has felt attribution disappear after a re-upload, a trim, or a platform handoff.

Most creators only need Creator Hub. If you're building a platform or watermarking catalogs at scale, you'll also want the Platform API.

If you care about being credited for audio you made, Creator Hub is where you start.