Openwhyd vs The Office API

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

Uptime · 30d
Uptime · 90d98.0%99.02%
Uptime · 30d100%100%
P50 · ms2191459
P95 · ms10552468
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — limits not published
Rate limit100 req/window · 99 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Openwhyd vs The Office API: common questions

Which is more reliable, Openwhyd or The Office API?

On our scheduled checks, The Office API leads on measured uptime — Openwhyd at 98.0% versus The Office API at 99.02% 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, Openwhyd or The Office API?

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

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

Can I call Openwhyd and The Office API from the browser?

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

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