Platforms that host user uploads can screen every file against the catalogs of the rights-holders they work with. Riffhold is part of the withConflux Content API, so it uses the same key, endpoint and billing as your other checks.
First register tracks. Send a link to the audio, or upload the file, to /api/v1/riffhold/tracks with a title and, if you have them, an ISRC and the rights owner. The call returns once the track is fingerprinted. You can list and remove tracks over the same route.
Then check uploads. Call /api/v1/check with needs set to audio-ownership and the asset's URL. If you know who uploaded it, pass that as owner: when the uploader is the track's rights owner, the verdict is own duplicate instead of a match, so artists can post their own music without being flagged.
The response tells you what to do. Owned means an exact file or segment match. Protected means the same recording, re-encoded or trimmed. Review means similar but not certain and should go to a person. Clear means no match. Each result includes the confidence, the matched track and the aligned span in seconds, so a moderator can verify it quickly.
Riffhold checks show up in your request log, spend caps and invoices like any other need. A typical check takes one to two seconds. For catalogs of more than 1,000 tracks, talk to us and we help you set up the import.