shipapis
StarSubmit an APISubmit API

Longevity World Cup vs RacingHub

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

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

Longevity World Cup vs RacingHub: common questions

Which is more reliable, Longevity World Cup or RacingHub?

On our scheduled checks, RacingHub leads on measured uptime — Longevity World Cup 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 Longevity World Cup and RacingHub need an API key?

Neither needs a paid key — Longevity World Cup 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 Longevity World Cup and RacingHub from the browser?

Yes — both Longevity World Cup and RacingHub send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Longevity World Cup and RacingHub free for commercial use?

Longevity World Cup 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.