Squiggle vs TheCocktailDB

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Squiggle vs TheCocktailDB: common questions

Which is more reliable, Squiggle or TheCocktailDB?

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

Neither needs a paid key — Squiggle is callable with no signup, and TheCocktailDB is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Squiggle and TheCocktailDB from the browser?

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

Are Squiggle and TheCocktailDB free for commercial use?

Squiggle has unclear commercial terms, and TheCocktailDB 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.