Hyrule Compendium vs Open5e

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

Uptime · 30d
Uptime · 90d100%89.2%
Uptime · 30d100%85.0%
P50 · ms460646
P95 · ms11464308
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedSRD content under OGL 1.0a; API/site MIT-licensed
Free tierFree — no API keyFree, no API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hyrule Compendium vs Open5e: common questions

Which is more reliable, Hyrule Compendium or Open5e?

On our scheduled checks, Hyrule Compendium leads on measured uptime — Hyrule Compendium 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, Hyrule Compendium or Open5e?

Hyrule Compendium has the lower median latency in our checks — Hyrule Compendium responds in 460 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 Hyrule Compendium and Open5e need an API key?

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

Can I call Hyrule Compendium and Open5e from the browser?

Yes — both Hyrule Compendium and Open5e 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 Hyrule Compendium and Open5e free for commercial use?

Hyrule Compendium 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.