0x vs Block Lottos

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%96.7%
P50 · ms6221025
P95 · ms34213658
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

0x vs Block Lottos: common questions

Which is more reliable, 0x or Block Lottos?

On our scheduled checks, 0x leads on measured uptime — 0x at 100% versus Block Lottos at 98.0% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, 0x or Block Lottos?

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

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

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

0x 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.