Makeup vs openFDA API

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms791806
P95 · ms25291868
Authnonenone
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Makeup vs openFDA API: common questions

Which is more reliable, Makeup or openFDA API?

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

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

Neither needs a paid key — Makeup is callable with no signup, and openFDA API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Makeup and openFDA API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Makeup 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 Makeup and openFDA API free for commercial use?

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