shipapis
StarSubmit an APISubmit API

Excuser vs TasteDive

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

APIExcuserNEW—TasteDiveNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Excuser vs TasteDive: common questions

Which is more reliable, Excuser or TasteDive?

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

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

Can I call Excuser and TasteDive from the browser?

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

Are Excuser and TasteDive free for commercial use?

Excuser has unclear commercial terms, and TasteDive 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.