shipapis
StarSubmit an APISubmit API

Openwhyd vs Radio Browser

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

APIOpenwhydHEALTHY84Radio BrowserHEALTHY90
Uptime · 30d
Uptime · 90d98.0%95.1%
Uptime · 30d100%98.3%
P50 · ms219556
P95 · ms10552431
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree and open source — no key
Rate limit100 req/window · 99 remaining · resets 60Unpublished (clients asked to send a descriptive User-Agent)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Openwhyd vs Radio Browser: common questions

Which is more reliable, Openwhyd or Radio Browser?

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

Openwhyd has the lower median latency in our checks — Openwhyd responds in 219 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 Openwhyd and Radio Browser need an API key?

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

Can I call Openwhyd and Radio Browser from the browser?

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

Are Openwhyd and Radio Browser free for commercial use?

Openwhyd 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.