Openwhyd vs Wallhaven

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

Uptime · 30d
Uptime · 90d98.0%82.4%
Uptime · 30d100%71.7%
P50 · ms219625
P95 · ms10553981
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree tier — key may be required
Rate limit100 req/window · 99 remaining · resets 6045 req/window · 44 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Openwhyd vs Wallhaven: common questions

Which is more reliable, Openwhyd or Wallhaven?

On our scheduled checks, Openwhyd leads on measured uptime — Openwhyd at 98.0% 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, Openwhyd or Wallhaven?

Openwhyd has the lower median latency in our checks — Openwhyd responds in 219 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 Openwhyd and Wallhaven need an API key?

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

Can I call Openwhyd and Wallhaven from the browser?

Neither sends browser-friendly CORS headers reliably, so call Openwhyd and Wallhaven from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Openwhyd and Wallhaven free for commercial use?

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