TasteDive vs justmeme.wtf

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — no key
Rate limitUnpublished60 requests/minute per IP (per docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

TasteDive vs justmeme.wtf: common questions

Which is more reliable, TasteDive or justmeme.wtf?

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

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

Can I call TasteDive and justmeme.wtf from the browser?

Only justmeme.wtf is browser-friendly — it returns CORS headers over HTTPS. TasteDive needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are TasteDive and justmeme.wtf free for commercial use?

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