Musixmatch vs Radio Browser

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%95.1%
Uptime · 30d100%98.3%
P50 · ms559556
P95 · ms14862431
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree and open source — no key
Rate limitUnpublishedUnpublished (clients asked to send a descriptive User-Agent)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Musixmatch vs Radio Browser: common questions

Which is more reliable, Musixmatch or Radio Browser?

On our scheduled checks, Musixmatch leads on measured uptime — Musixmatch at 100% versus Radio Browser at 95.1% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Musixmatch or Radio Browser?

Radio Browser has the lower median latency in our checks — Musixmatch responds in 559 ms versus Radio Browser at 556 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Musixmatch and Radio Browser need an API key?

Radio Browser needs no key, while Musixmatch requires a free API key. If you want to start calling without signup, reach for Radio Browser first.

Can I call Musixmatch and Radio Browser from the browser?

Only Radio Browser is browser-friendly — it returns CORS headers over HTTPS. Musixmatch needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Musixmatch and Radio Browser free for commercial use?

Musixmatch has unclear commercial terms, and Radio Browser has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.