shipapis
StarSubmit an APISubmit API

LAPIS vs Longevity World Cup

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

APILAPISHEALTHY95Longevity World CupHEALTHY85
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms524767
P95 · ms8463677
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedUnverified
Free tierFree — no key (open instance)Free — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs Longevity World Cup: common questions

Which is more reliable, LAPIS or Longevity World Cup?

On our scheduled checks, LAPIS leads on measured uptime — LAPIS at 100% versus Longevity World Cup at 99.02% 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 Longevity World Cup?

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

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

Can I call LAPIS and Longevity World Cup from the browser?

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

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