An API of Ice And Fire vs Metropolitan Museum of Art

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC0 1.0 (Open Access data)
Free tierFree, no keyFree, no API key required
Rate limitUnpublished80 requests/second (requested in docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

An API of Ice And Fire vs Metropolitan Museum of Art: common questions

Which is more reliable, An API of Ice And Fire or Metropolitan Museum of Art?

On our scheduled checks, Metropolitan Museum of Art leads on measured uptime — An API of Ice And Fire at —% versus Metropolitan Museum of Art 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 Metropolitan Museum of Art need an API key?

Neither needs a paid key — An API of Ice And Fire is callable with no signup, and Metropolitan Museum of Art 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 Metropolitan Museum of Art from the browser?

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

An API of Ice And Fire has unclear commercial terms, and Metropolitan Museum of Art allows commercial use on its free tier. 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.