Lexigram vs openFDA API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnono
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 API: common questions

Which is more reliable, Lexigram or openFDA API?

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

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

Can I call Lexigram and openFDA API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Lexigram and openFDA API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Lexigram and openFDA API free for commercial use?

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