Memesio vs TasteDive

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierPublic metadata endpoints keyless; generation needs an API keyFree tier — key may be required
Rate limit80 req/window · 79 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Memesio vs TasteDive: common questions

Which is more reliable, Memesio or TasteDive?

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

Memesio needs no key, while TasteDive requires a free API key. If you want to start calling without signup, reach for Memesio first.

Can I call Memesio and TasteDive from the browser?

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

Are Memesio and TasteDive free for commercial use?

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