shipapis
StarSubmit an APISubmit API

Block Lottos vs Sharpe

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

APIBlock LottosHEALTHY87SharpeHEALTHY81
Uptime · 30d
Uptime · 90d98.0%98.0%
Uptime · 30d96.7%96.7%
P50 · ms10251239
P95 · ms36583358
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no key (API docs state no key required)Free — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Block Lottos vs Sharpe: common questions

Which is more reliable, Block Lottos or Sharpe?

Both are neck-and-neck — Block Lottos and Sharpe each measure 98.0% 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, Block Lottos or Sharpe?

Block Lottos has the lower median latency in our checks — Block Lottos responds in 1025 ms versus Sharpe at 1239 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 Block Lottos and Sharpe need an API key?

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

Can I call Block Lottos and Sharpe from the browser?

Yes — both Block Lottos and Sharpe 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 Block Lottos and Sharpe free for commercial use?

Block Lottos has unclear commercial terms, and Sharpe 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.