shipapis
StarSubmit an APISubmit API

LAPIS vs SportScore

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

APILAPISHEALTHY95SportScoreHEALTHY71
Uptime · 30d
Uptime · 90d100%87.3%
Uptime · 30d100%86.7%
P50 · ms524288
P95 · ms8462112
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedUnverified
Free tierFree — no key (open instance)Free — no key (attribution tier)
Rate limitUnpublishedRetry-After: 5s
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs SportScore: common questions

Which is more reliable, LAPIS or SportScore?

On our scheduled checks, LAPIS leads on measured uptime — LAPIS at 100% versus SportScore at 87.3% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, LAPIS or SportScore?

SportScore has the lower median latency in our checks — LAPIS responds in 524 ms versus SportScore at 288 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 LAPIS and SportScore need an API key?

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

Can I call LAPIS and SportScore from the browser?

Only LAPIS is browser-friendly — it returns CORS headers over HTTPS. SportScore needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are LAPIS and SportScore free for commercial use?

LAPIS has unclear commercial terms, and SportScore 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.