shipapis
StarSubmit an APISubmit API

ClinicalTrials.gov vs Open Food Facts

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

APIClinicalTrials.govNEW—Open Food FactsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
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

ClinicalTrials.gov vs Open Food Facts: common questions

Which is more reliable, ClinicalTrials.gov or Open Food Facts?

On our scheduled checks, Open Food Facts leads on measured uptime — ClinicalTrials.gov at —% versus Open Food Facts 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 ClinicalTrials.gov and Open Food Facts need an API key?

Neither needs a paid key — ClinicalTrials.gov is callable with no signup, and Open Food Facts is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ClinicalTrials.gov and Open Food Facts from the browser?

Yes — both ClinicalTrials.gov and Open Food Facts send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are ClinicalTrials.gov and Open Food Facts free for commercial use?

ClinicalTrials.gov has unclear commercial terms, and Open Food Facts 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.