MediaCaption API vs Radio Browser

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1062587
P95 · ms10621064
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUnverified
Free tier10 credits when you sign upFree and open source — no key
Rate limit60 req/minUnpublished (clients asked to send a descriptive User-Agent)
In directory since2026-07-182026-07-05
operationalpartialdownno data

MediaCaption API vs Radio Browser: common questions

Which is more reliable, MediaCaption API or Radio Browser?

Both are neck-and-neck — MediaCaption API and Radio Browser each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, MediaCaption API or Radio Browser?

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

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

Can I call MediaCaption API and Radio Browser from the browser?

Yes — both MediaCaption API and Radio Browser send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are MediaCaption API and Radio Browser free for commercial use?

MediaCaption API allows commercial use on its free tier, 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.