shipapis
StarSubmit an APISubmit API

Memesio vs Agify

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

APIMemesioNEW—AgifyHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedProprietary
Free tierPublic metadata endpoints keyless; generation needs an API key100 names/day, no signup
Rate limit80 req/window · 79 remaining100/day per IP
In directory since2026-07-052026-05-02
operationalpartialdownno data

Memesio vs Agify: common questions

Which is more reliable, Memesio or Agify?

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

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

Can I call Memesio and Agify from the browser?

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

Are Memesio and Agify free for commercial use?

Memesio 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.