shipapis
StarSubmit an APISubmit API

BMI Calculator API vs LAPIS

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

APIBMI Calculator APIHEALTHY80LAPISHEALTHY95
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1350524
P95 · ms2314846
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — limits not publishedFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BMI Calculator API vs LAPIS: common questions

Which is more reliable, BMI Calculator API or LAPIS?

Both are neck-and-neck — BMI Calculator API and LAPIS each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, BMI Calculator API or LAPIS?

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

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

Can I call BMI Calculator API and LAPIS from the browser?

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

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