Genrenator vs Wallhaven

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

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

Genrenator vs Wallhaven: common questions

Which is more reliable, Genrenator or Wallhaven?

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

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

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

Can I call Genrenator and Wallhaven from the browser?

Only Genrenator 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 Genrenator and Wallhaven free for commercial use?

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