shipapis
StarSubmit an APISubmit API

Lexigram vs Open Disease

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

APILexigramNEW—Open DiseaseNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree tier — key may be requiredFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs Open Disease: common questions

Which is more reliable, Lexigram or Open Disease?

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

Open Disease needs no key, while Lexigram requires a free API key. If you want to start calling without signup, reach for Open Disease first.

Can I call Lexigram and Open Disease from the browser?

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

Are Lexigram and Open Disease free for commercial use?

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