Bevwire API vs RecipeAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs RecipeAPI: common questions

Which is more reliable, Bevwire API or RecipeAPI?

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

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

Can I call Bevwire API and RecipeAPI from the browser?

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

Are Bevwire API and RecipeAPI free for commercial use?

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