shipapis
StarSubmit an APISubmit API

ClinicalTrials.gov vs Coffee

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

APIClinicalTrials.govHEALTHY78CoffeeHEALTHY94
Uptime · 30d
Uptime · 90d100%99.44%
Uptime · 30d100%100%
P50 · ms138370
P95 · ms35332826
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no API key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClinicalTrials.gov vs Coffee: common questions

Which is more reliable, ClinicalTrials.gov or Coffee?

On our scheduled checks, ClinicalTrials.gov leads on measured uptime — ClinicalTrials.gov at 100% versus Coffee at 99.44% 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, ClinicalTrials.gov or Coffee?

ClinicalTrials.gov has the lower median latency in our checks — ClinicalTrials.gov responds in 138 ms versus Coffee at 370 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 ClinicalTrials.gov and Coffee need an API key?

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

Can I call ClinicalTrials.gov and Coffee from the browser?

Only ClinicalTrials.gov is browser-friendly — it returns CORS headers over HTTPS. Coffee needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ClinicalTrials.gov and Coffee free for commercial use?

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