OMDb vs Openwhyd

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%100%
P50 · ms188219
P95 · ms11401055
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseCommunity-contributed metadataUnverified
Free tier1,000 req/day free keyFree — no key required
Rate limitPatron key `trilogy` is shared — cache responses100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

OMDb vs Openwhyd: common questions

Which is more reliable, OMDb or Openwhyd?

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

OMDb has the lower median latency in our checks — OMDb responds in 188 ms versus Openwhyd at 219 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 Openwhyd need an API key?

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

Can I call OMDb and Openwhyd from the browser?

Only OMDb is browser-friendly — it returns CORS headers over HTTPS. Openwhyd needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are OMDb and Openwhyd free for commercial use?

OMDb has unclear commercial terms, and Openwhyd 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.