Search Jamendo's catalog and correctly apply licensing/usage parameters for royalty-free (Creative Commons) music
domain: developer.jamendo.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a client on developer.jamendo.com to get a client_id for API access
Call the tracks search method (v3.0) with your client_id and search parameters (search, tags, fuzzytags, acousticelectric, vocalinstrumental, etc.) to find candidate tracks
Add `include=licenses` (alongside other `include` values like musicinfo, stats, lyrics as needed) to get each track's Creative Commons / Jamendo Pro licensing details in the same response
Check whether your intended use is non-commercial or commercial: the free API is usable for non-commercial applications, while commercial use requires contacting Jamendo for a separate licensing quote
For actual royalty-free licensing/clearance for commercial sync use (not just discovery), use Jamendo Licensing's separate catalog/licensing product rather than assuming API search access alone grants usage rights
Read each track's specific Creative Commons license variant (e.g. attribution requirements, share-alike, non-commercial-only) before reusing it, since not all CC tracks in the catalog carry the same terms
Known gotchas
Being able to fetch a track via the free API does not automatically mean you have commercial usage rights to it — CC license terms per-track (and Jamendo's non-commercial-only free-API policy) both need checking
License details are only returned when you explicitly request `include=licenses`; a plain search response can omit the very field you need to confirm you're allowed to use the track
Jamendo's discovery API (developer.jamendo.com) and Jamendo Licensing (licensing.jamendo.com) are related but distinct products — royalty-free commercial licensing workflows go through Licensing, not just the open API
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?