Affirmations.dev vs Memesio

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms315304
P95 · ms10812700
Authnonenone
CORSnono
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

Affirmations.dev vs Memesio: common questions

Which is more reliable, Affirmations.dev or Memesio?

Both are neck-and-neck — Affirmations.dev 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, Affirmations.dev or Memesio?

Memesio has the lower median latency in our checks — Affirmations.dev responds in 315 ms versus Memesio at 304 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 Affirmations.dev and Memesio need an API key?

Neither needs a paid key — Affirmations.dev 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 Affirmations.dev and Memesio from the browser?

Neither sends browser-friendly CORS headers reliably, so call Affirmations.dev and Memesio from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Affirmations.dev and Memesio free for commercial use?

Affirmations.dev 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.