shipapis
StarSubmit an APISubmit API

IMDbOT vs Openwhyd

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

APIIMDbOTDEAD0OpenwhydHEALTHY77
Uptime · 30d
Uptime · 90d0.0%97.2%
Uptime · 30d0.0%100%
P50 · ms—141
P95 · ms—1350
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

IMDbOT vs Openwhyd: common questions

Which is more reliable, IMDbOT or Openwhyd?

On our scheduled checks, Openwhyd leads on measured uptime — IMDbOT at 0.0% versus Openwhyd at 97.2% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do IMDbOT and Openwhyd need an API key?

Neither needs a paid key — IMDbOT is callable with no signup, and Openwhyd is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IMDbOT and Openwhyd from the browser?

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

Are IMDbOT and Openwhyd free for commercial use?

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