shipapis
StarSubmit an APISubmit API

Excuser vs TasteDive

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

APIExcuserHEALTHY96TasteDiveHEALTHY95
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms303325
P95 · ms9322265
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?

Both are neck-and-neck — Excuser and TasteDive each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Excuser or TasteDive?

Excuser has the lower median latency in our checks — Excuser responds in 303 ms versus TasteDive at 325 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 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.