shipapis
StarSubmit an APISubmit API

Agify vs kimiquotes

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

APIAgifyHEALTHY—kimiquotesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseProprietaryUnverified
Free tier100 names/day, no signupFree — limits not published
Rate limit100/day per IPUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

Agify vs kimiquotes: common questions

Which is more reliable, Agify or kimiquotes?

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

Neither needs a paid key — Agify is callable with no signup, and kimiquotes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Agify and kimiquotes from the browser?

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

Are Agify and kimiquotes free for commercial use?

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