OMDb vs Wallhaven

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

Uptime · 30d
Uptime · 90d100%82.4%
Uptime · 30d100%71.7%
P50 · ms188625
P95 · ms11403981
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseCommunity-contributed metadataUnverified
Free tier1,000 req/day free keyFree tier — key may be required
Rate limitPatron key `trilogy` is shared — cache responses45 req/window · 44 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

OMDb vs Wallhaven: common questions

Which is more reliable, OMDb or Wallhaven?

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

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

Both ask you to authenticate — OMDb uses an API key and Wallhaven uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call OMDb and Wallhaven from the browser?

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

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