ES·pera API vs Open Disease

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

Uptime · 30d
Uptime · 90d0.0%99.44%
Uptime · 30d0.0%100%
P50 · ms—217
P95 · ms—1159
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (sources vary; see project repo)
Free tierFree — no key required
Rate limitUnpublished
In directory since2026-09-212026-07-05
operationalpartialdownno data

ES·pera API vs Open Disease: common questions

Which is more reliable, ES·pera API or Open Disease?

On our scheduled checks, Open Disease leads on measured uptime — ES·pera API at 0.0% versus Open Disease at 99.44% 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 ES·pera API and Open Disease need an API key?

Neither needs a paid key — ES·pera API is callable with no signup, and Open Disease is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ES·pera API and Open Disease from the browser?

Only Open Disease is browser-friendly — it returns CORS headers over HTTPS. ES·pera API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ES·pera API and Open Disease free for commercial use?

ES·pera API has unclear commercial terms, and Open Disease 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.