Lexigram vs openFDA

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

Uptime · 30d
Uptime · 90d99.02%94.1%
Uptime · 30d98.3%93.3%
P50 · ms8071187
P95 · ms16724661
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs openFDA: common questions

Which is more reliable, Lexigram or openFDA?

On our scheduled checks, Lexigram leads on measured uptime — Lexigram at 99.02% versus openFDA at 94.1% 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, Lexigram or openFDA?

Lexigram has the lower median latency in our checks — Lexigram responds in 807 ms versus openFDA at 1187 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 Lexigram and openFDA need an API key?

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

Can I call Lexigram and openFDA from the browser?

Only openFDA 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 openFDA free for commercial use?

Lexigram has unclear commercial terms, and openFDA 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.