shipapis
StarSubmit an APISubmit API

Excuser vs Memesio

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

APIExcuserNEW—MemesioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedPublic metadata endpoints keyless; generation needs an API key
Rate limitUnpublished80 req/window · 79 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Excuser vs Memesio: common questions

Which is more reliable, Excuser or Memesio?

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

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

Can I call Excuser and Memesio from the browser?

Only Excuser 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 Excuser and Memesio free for commercial use?

Excuser has unclear commercial terms, and Memesio 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.