RecipeAPI vs Squiggle

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RecipeAPI vs Squiggle: common questions

Which is more reliable, RecipeAPI or Squiggle?

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

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

Can I call RecipeAPI and Squiggle from the browser?

Only RecipeAPI 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 RecipeAPI and Squiggle free for commercial use?

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