Harry Potter API vs Openwhyd

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

Uptime · 30d
Uptime · 90d100%97.2%
Uptime · 30d100%100%
P50 · ms154141
P95 · ms7951350
Authnonenone
CORSyesno
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

Harry Potter API vs Openwhyd: common questions

Which is more reliable, Harry Potter API or Openwhyd?

On our scheduled checks, Harry Potter API leads on measured uptime — Harry Potter API at 100% 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.

Which is faster, Harry Potter API or Openwhyd?

Openwhyd has the lower median latency in our checks — Harry Potter API responds in 154 ms versus Openwhyd at 141 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 Harry Potter API and Openwhyd need an API key?

Neither needs a paid key — Harry Potter API 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 Harry Potter API and Openwhyd from the browser?

Only Harry Potter API 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 Harry Potter API and Openwhyd free for commercial use?

Harry Potter API 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.