shipapis
StarSubmit an APISubmit API

TasteDive vs Agify

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

APITasteDiveUNMONITORED—AgifyHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedProprietary
Free tierFree tier — key may be required100 names/day, no signup
Rate limitUnpublished100/day per IP
In directory since2026-07-052026-05-02
operationalpartialdownno data

TasteDive vs Agify: common questions

Which is more reliable, TasteDive or Agify?

Only Agify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do TasteDive and Agify need an API key?

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

Can I call TasteDive and Agify from the browser?

Only Agify 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 TasteDive and Agify free for commercial use?

TasteDive has unclear commercial terms, and Agify allows commercial use on its free tier. 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.