Bevwire API vs DiscGolf

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms701762
P95 · ms19002153
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedFree to use with attribution (per response metadata)
Free tierFree — limits not publishedFree — public endpoints, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs DiscGolf: common questions

Which is more reliable, Bevwire API or DiscGolf?

Both are neck-and-neck — Bevwire API and DiscGolf each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Bevwire API or DiscGolf?

Bevwire API has the lower median latency in our checks — Bevwire API responds in 701 ms versus DiscGolf at 762 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Bevwire API and DiscGolf need an API key?

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

Can I call Bevwire API and DiscGolf from the browser?

Only DiscGolf 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 DiscGolf free for commercial use?

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