Battle.net vs Open5e

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

Uptime · 30d
Uptime · 90d100%89.2%
Uptime · 30d100%85.0%
P50 · ms1024646
P95 · ms31734308
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedSRD content under OGL 1.0a; API/site MIT-licensed
Free tierFree tier — key may be requiredFree, no API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs Open5e: common questions

Which is more reliable, Battle.net or Open5e?

On our scheduled checks, Battle.net leads on measured uptime — Battle.net at 100% versus Open5e at 89.2% 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, Battle.net or Open5e?

Open5e has the lower median latency in our checks — Battle.net responds in 1024 ms versus Open5e at 646 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 Battle.net and Open5e need an API key?

Open5e needs no key, while Battle.net requires a free API key. If you want to start calling without signup, reach for Open5e first.

Can I call Battle.net and Open5e from the browser?

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

Are Battle.net and Open5e free for commercial use?

Battle.net has unclear commercial terms, and Open5e 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.