shipapis
StarSubmit an APISubmit API

Bevwire API vs Fruityvice

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

APIBevwire APINEW—FruityviceNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no API key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs Fruityvice: common questions

Which is more reliable, Bevwire API or Fruityvice?

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

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

Can I call Bevwire API and Fruityvice from the browser?

Neither sends browser-friendly CORS headers reliably, so call Bevwire API and Fruityvice from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Bevwire API and Fruityvice free for commercial use?

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