An API of Ice And Fire vs Wallhaven

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

Uptime · 30d
Uptime · 90d100%82.4%
Uptime · 30d100%71.7%
P50 · ms46625
P95 · ms12923981
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no keyFree tier — key may be required
Rate limitUnpublished45 req/window · 44 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

An API of Ice And Fire vs Wallhaven: common questions

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

On our scheduled checks, An API of Ice And Fire leads on measured uptime — An API of Ice And Fire at 100% versus Wallhaven at 82.4% 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, An API of Ice And Fire or Wallhaven?

An API of Ice And Fire has the lower median latency in our checks — An API of Ice And Fire responds in 46 ms versus Wallhaven at 625 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 An API of Ice And Fire and Wallhaven need an API key?

An API of Ice And Fire needs no key, while Wallhaven requires a free API key. If you want to start calling without signup, reach for An API of Ice And Fire first.

Can I call An API of Ice And Fire and Wallhaven from the browser?

Only An API of Ice And Fire is browser-friendly — it returns CORS headers over HTTPS. Wallhaven needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are An API of Ice And Fire and Wallhaven free for commercial use?

An API of Ice And Fire has unclear commercial terms, and Wallhaven 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.