shipapis
StarSubmit an APISubmit API

Foodish vs SharpAPI

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

APIFoodishDYING53SharpAPIDEAD0
Uptime · 30d
Uptime · 90d27.5%0.0%
Uptime · 30d11.7%0.0%
P50 · ms250—
P95 · ms760—
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)Unverified
Free tierFree — no keyFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs SharpAPI: common questions

Which is more reliable, Foodish or SharpAPI?

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

Foodish needs no key, while SharpAPI requires a free API key. If you want to start calling without signup, reach for Foodish first.

Can I call Foodish and SharpAPI from the browser?

Only SharpAPI 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 Foodish and SharpAPI free for commercial use?

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