shipapis
StarSubmit an APISubmit API

LAPIS vs RacingHub

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

APILAPISNEW—RacingHubNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedCC BY 4.0 (source data from the F1DB project)
Free tierFree — no key (open instance)Free — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs RacingHub: common questions

Which is more reliable, LAPIS or RacingHub?

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

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

Yes — both LAPIS 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 LAPIS and RacingHub free for commercial use?

LAPIS 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.