Bevwire API vs ES·pera API

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

Uptime · 30d
Uptime · 90d71.1%0.0%
Uptime · 30d13.3%0.0%
P50 · ms477—
P95 · ms1900—
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-09-21
operationalpartialdownno data

Bevwire API vs ES·pera API: common questions

Which is more reliable, Bevwire API or ES·pera API?

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

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

Can I call Bevwire API and ES·pera API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Bevwire API and ES·pera API 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 ES·pera API free for commercial use?

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