F1 API vs Open Disease

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

F1 API vs Open Disease: common questions

Which is more reliable, F1 API or Open Disease?

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

Neither needs a paid key — F1 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 F1 API and Open Disease from the browser?

Yes — both F1 API and Open Disease 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 F1 API and Open Disease free for commercial use?

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