shipapis
StarSubmit an APISubmit API

CIE-10 API vs Coffee

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

APICIE-10 APIHEALTHY91CoffeeHEALTHY89
Uptime · 30d
Uptime · 90d94.1%99.02%
Uptime · 30d100%98.3%
P50 · ms466698
P95 · ms9912826
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no API key
Rate limit120 req/window · 119 remaining · resets 1783518425Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CIE-10 API vs Coffee: common questions

Which is more reliable, CIE-10 API or Coffee?

On our scheduled checks, Coffee leads on measured uptime — CIE-10 API at 94.1% versus Coffee at 99.02% 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, CIE-10 API or Coffee?

CIE-10 API has the lower median latency in our checks — CIE-10 API responds in 466 ms versus Coffee at 698 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 CIE-10 API and Coffee need an API key?

Neither needs a paid key — CIE-10 API 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 CIE-10 API and Coffee from the browser?

Only CIE-10 API 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 CIE-10 API and Coffee free for commercial use?

CIE-10 API 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.