IMDbOT vs Radio Browser

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

Uptime · 30d
Uptime · 90d25.5%95.1%
Uptime · 30d0.0%98.3%
P50 · ms1208556
P95 · ms17392431
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree and open source — no key
Rate limitUnpublishedUnpublished (clients asked to send a descriptive User-Agent)
In directory since2026-07-052026-07-05
operationalpartialdownno data

IMDbOT vs Radio Browser: common questions

Which is more reliable, IMDbOT or Radio Browser?

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

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

Neither needs a paid key — IMDbOT 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 IMDbOT and Radio Browser from the browser?

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

Are IMDbOT and Radio Browser free for commercial use?

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