An API of Ice And Fire vs Radio Browser

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no keyFree and open source — no key
Rate limitUnpublishedUnpublished (clients asked to send a descriptive User-Agent)
In directory since2026-07-052026-07-05
operationalpartialdownno data

An API of Ice And Fire vs Radio Browser: common questions

Which is more reliable, An API of Ice And Fire or Radio Browser?

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

Do An API of Ice And Fire and Radio Browser need an API key?

Neither needs a paid key — An API of Ice And Fire 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 An API of Ice And Fire and Radio Browser from the browser?

Yes — both An API of Ice And Fire 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 An API of Ice And Fire and Radio Browser free for commercial use?

An API of Ice And Fire 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.