CryptAPI vs Block Lottos

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseUnverifiedUnverified
Free tierFree API; provider takes ~1% fee per forwarded paymentFree, no key (API docs state no key required)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CryptAPI vs Block Lottos: common questions

Which is more reliable, CryptAPI or Block Lottos?

On our scheduled checks, Block Lottos leads on measured uptime — CryptAPI at —% versus Block Lottos 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 CryptAPI and Block Lottos need an API key?

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

Can I call CryptAPI and Block Lottos from the browser?

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

CryptAPI allows commercial use on its free tier, and Block Lottos 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.