OMDb vs Poof

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseCommunity-contributed metadataUnverified
Free tier1,000 req/day free keyFree tier — API key required
Rate limitPatron key `trilogy` is shared — cache responsesUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OMDb vs Poof: common questions

Which is more reliable, OMDb or Poof?

On our scheduled checks, Poof leads on measured uptime — OMDb at —% versus Poof at —% 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 OMDb and Poof need an API key?

Both ask you to authenticate — OMDb uses an API key and Poof 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 Poof from the browser?

Yes — both OMDb and Poof send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are OMDb and Poof free for commercial use?

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