Bevwire API vs Lexigram

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

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

Bevwire API vs Lexigram: common questions

Which is more reliable, Bevwire API or Lexigram?

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

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

Can I call Bevwire API and Lexigram from the browser?

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

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