shipapis
StarSubmit an APISubmit API

Block Lottos vs Sharpe

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

APIBlock LottosNEW—SharpeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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?

On our scheduled checks, Sharpe leads on measured uptime — Block Lottos at —% versus Sharpe 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 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?

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

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.