Radio Browser vs Verome

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

Uptime · 30d
Uptime · 90d95.1%38.2%
Uptime · 30d98.3%0.0%
P50 · ms556884
P95 · ms24314329
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree and open source — no keyFree — limits not published
Rate limitUnpublished (clients asked to send a descriptive User-Agent)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Radio Browser vs Verome: common questions

Which is more reliable, Radio Browser or Verome?

On our scheduled checks, Radio Browser leads on measured uptime — Radio Browser at 95.1% versus Verome at 38.2% 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, Radio Browser or Verome?

Radio Browser has the lower median latency in our checks — Radio Browser responds in 556 ms versus Verome at 884 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 Radio Browser and Verome need an API key?

Neither needs a paid key — Radio Browser is callable with no signup, and Verome is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Radio Browser and Verome from the browser?

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

Are Radio Browser and Verome free for commercial use?

Radio Browser has unclear commercial terms, and Verome 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.