Block Lottos vs CryptAPI

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

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

Block Lottos vs CryptAPI: common questions

Which is more reliable, Block Lottos or CryptAPI?

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

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

Can I call Block Lottos and CryptAPI from the browser?

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

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