shipapis
StarSubmit an APISubmit API

openFDA API vs Squiggle

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

APIopenFDA APINEW—SquiggleNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

openFDA API vs Squiggle: common questions

Which is more reliable, openFDA API or Squiggle?

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

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

Can I call openFDA API and Squiggle from the browser?

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

Are openFDA API and Squiggle free for commercial use?

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