If your platform hosts user video or audio, a single clip with a commercial track behind it can mean a takedown, a muted upload, or a copyright strike. Music-rights screening catches that before you publish — not after a claim lands.
Key takeaways
- Screening fingerprints audio and matches it against commercial catalogs.
- Catch copyrighted tracks pre-publish to avoid takedowns and strikes.
- It's a check you can run one-off for free, or wire into your upload path.
- On a gateway it shares the same key and bill as your other checks.
Why screen pre-publish
Platforms increasingly auto-detect copyrighted music and act on it — muting, blocking, or penalizing the account. If you let users post first and find out later, the damage (and the support load) is already done. Screening at upload turns a reactive problem into a quiet gate.
How it works
The check generates an acoustic fingerprint of the audio and matches it against commercial music catalogs. A match comes back with the track and rights metadata, so you can warn the user, block the upload, or route it for review.
Screening tells you a track is recognized commercial music — not whether a given user is licensed. Use it to flag and inform, then apply your own policy.
Try it free
The Music Rights Check screens an audio or video file with no signup. Same engine as the API, so the result is production-accurate.
Into your pipeline
- Test the free check against clips you know, to calibrate your policy.
- Call the same capability at upload via your withConflux key.
- Combine it with moderation and AI-image detection on one integration — one gateway covers them all.
Don't find out from a takedown. Screen it first — free.