Question 1

How does Riffwarden monitor a registered catalog, and which channels are supported?

Accepted Answer

Riffwarden registers your tracks and monitors supported channels for potential uses, then surfaces detected platform matches in your catalog workflow. Current channel coverage includes YouTube, TikTok, Twitch, podcasts, and live radio. Coverage depends on the channel, territory, reference data, and monitoring configuration, so it is not universal and detection is not guaranteed.

Question 2

What happens when Riffwarden flags a possible infringement?

Accepted Answer

A flagged match enters review with its available evidence and an action status. You can approve or reject the match, then take an available action such as preparing or filing a DMCA notice or claim where applicable. Platform responses and follow-up activity stay attached to the original match. Not every match is automatically actioned, and a detected match is not by itself a legal conclusion.

Question 3

How are PRO, DSP, and MLC recoveries tracked?

Accepted Answer

Riffwarden tracks recovery claims and statuses for PRO filings, DSP claims, and MLC unmatched-mechanical targets in the same workspace as the source match. The dashboard records where a claim is in its review, filing, acknowledgment, or recovery flow; the target organization determines eligibility, payout amount, and timing, so Riffwarden does not guarantee a recovery or a payment date.

Question 4

What does the Label tier include?

Accepted Answer

Label is custom-priced and contact-led for teams managing more than one artist. It adds multi-artist and per-artist views, higher track capacity, custom monitoring, a concierge takedown and recovery workflow, and an audit trail for operational follow-through. The exact scope is shaped around your catalog and workflow rather than a one-size-fits-all public price.

Question 5

What can the public Riffwarden API do?

Accepted Answer

The public API provides authenticated read access for integrations that need catalog, infringement, earnings, and recovery data. Requests use a bearer key, are scoped to the caller’s workspace, and support paginated GET endpoints. It is not an open API: it does not claim to provide write operations or webhooks, and a key must be issued for the workspace that owns the data.

Clear answers for the work between detection and recovery.

Five questions, without the fine print doing the hiding.

See the commercial path or the integration surface.

Clear answers for the work between detection and recovery.

Five questions, without the fine print doing the hiding.

01How does Riffwarden monitor a registered catalog, and which channels are supported?

02What happens when Riffwarden flags a possible infringement?

03How are PRO, DSP, and MLC recoveries tracked?

04What does the Label tier include?

05What can the public Riffwarden API do?

See the commercial path or the integration surface.