shipapis
StarSubmit an APISubmit API

Bevwire API vs RacingHub

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

APIBevwire APINEW—RacingHubNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedCC BY 4.0 (source data from the F1DB project)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs RacingHub: common questions

Which is more reliable, Bevwire API or RacingHub?

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

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

Can I call Bevwire API and RacingHub from the browser?

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

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