shipapis
StarSubmit an APISubmit API

Agify vs TasteDive

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

APIAgifyHEALTHY—TasteDiveNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseProprietaryUnverified
Free tier100 names/day, no signupFree tier — key may be required
Rate limit100/day per IPUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

Agify vs TasteDive: common questions

Which is more reliable, Agify or TasteDive?

On our scheduled checks, TasteDive leads on measured uptime — Agify 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 Agify and TasteDive 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 Agify and TasteDive 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 Agify and TasteDive free for commercial use?

Agify allows commercial use on its free tier, 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.