GDBrowser vs LotteryData.io

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API keyFree tier — API key required
Rate limit150 req/window · 149 remaining · resets 1783513202Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GDBrowser vs LotteryData.io: common questions

Which is more reliable, GDBrowser or LotteryData.io?

On our scheduled checks, LotteryData.io leads on measured uptime — GDBrowser at —% versus LotteryData.io 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 GDBrowser and LotteryData.io need an API key?

GDBrowser needs no key, while LotteryData.io requires a free API key. If you want to start calling without signup, reach for GDBrowser first.

Can I call GDBrowser and LotteryData.io from the browser?

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

Are GDBrowser and LotteryData.io free for commercial use?

GDBrowser has unclear commercial terms, and LotteryData.io 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.