Music · head-to-head
Lyrics.ovh vs Radio Browser
Lyrics.ovh is a small keyless lookup service: GET a artist/title pair against api.lyrics.ovh/v1 and it fans that query out in parallel across sources like Genius, AZLyrics, and Letras.mus.br, returning the first full lyric text found as plain JSON. There's no authentication, no request quota, and no dashboard — it's a single open-source Node project (github.com/NTag/lyrics.ovh) that anyone can also self-host. The stored Apiary docs mirror has gone dead (502), but the live API itself responded with real lyrics during this check and sends a wildcard CORS header.
Radio Browser is a free, keyless, community-maintained directory of internet radio stations — over 60,000 of them — with search, tagging by genre/country/language, click-tracking, and ready-to-play M3U playlists for any station. It's fully open source, mirrored across several independently-run servers behind a round-robin DNS entry point, and its maintainers explicitly ask API consumers to pick a random mirror rather than hammer one instance. Responses are available as JSON or XML, with a dedicated M3U format for playlist endpoints.
| Lyrics.ovh | Radio Browser | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | JSON | JSON, XML, M3U |
| CORS | yes | yes |
| HTTPS | Yes | Yes |
Radio Browser supports 3 response formats, while Lyrics.ovh offers fewer — pick Radio Browser for more integration flexibility.