shipapis
StarSubmit an APISubmit API

CIE-10 API vs Foodish

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

APICIE-10 APIHEALTHY91FoodishDYING53
Uptime · 30d
Uptime · 90d94.1%27.5%
Uptime · 30d100%11.7%
P50 · ms466250
P95 · ms991760
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source)
Free tierFree — limits not publishedFree — no key
Rate limit120 req/window · 119 remaining · resets 1783518425Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CIE-10 API vs Foodish: common questions

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

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

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

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

Can I call CIE-10 API and Foodish from the browser?

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

Are CIE-10 API and Foodish free for commercial use?

CIE-10 API has unclear commercial terms, and Foodish 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.