shipapis
StarSubmit an APISubmit API

Verome vs Wallhaven

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

APIVeromeDEAD0WallhavenDYING82
Uptime · 30d
Uptime · 90d38.2%82.4%
Uptime · 30d0.0%71.7%
P50 · ms884625
P95 · ms43293981
AuthnoneapiKey
CORSnono
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

Verome vs Wallhaven: common questions

Which is more reliable, Verome or Wallhaven?

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

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

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

Can I call Verome and Wallhaven from the browser?

Neither sends browser-friendly CORS headers reliably, so call Verome 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 Verome and Wallhaven free for commercial use?

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