CryptoLabel API 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 useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no key (API docs state no key required)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CryptoLabel API vs Block Lottos: common questions

Which is more reliable, CryptoLabel API or Block Lottos?

Only Block Lottos is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do CryptoLabel API and Block Lottos need an API key?

Neither needs a paid key — CryptoLabel API 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 CryptoLabel API and Block Lottos from the browser?

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

CryptoLabel API has unclear commercial terms, 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.