Excuser vs Memesio

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms252398
P95 · ms9322700
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?

Both are neck-and-neck — Excuser and Memesio each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Excuser or Memesio?

Excuser has the lower median latency in our checks — Excuser responds in 252 ms versus Memesio at 398 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

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.