shipapis
StarSubmit an APISubmit API

Memesio vs TasteDive

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

APIMemesioHEALTHY94TasteDiveHEALTHY93
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms398561
P95 · ms27002265
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?

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

Memesio has the lower median latency in our checks — Memesio responds in 398 ms versus TasteDive at 561 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 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.