Holy Bible API vs Wolne Lektury

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

Uptime · 30d
Uptime · 90d100%75.5%
Uptime · 30d100%81.7%
P50 · ms8521145
P95 · ms22744998
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedWorks are public domain or on free/Creative Commons licenses (per WolneLektury); API terms not formally stated
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Holy Bible API vs Wolne Lektury: common questions

Which is more reliable, Holy Bible API or Wolne Lektury?

On our scheduled checks, Holy Bible API leads on measured uptime — Holy Bible API at 100% versus Wolne Lektury at 75.5% 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, Holy Bible API or Wolne Lektury?

Holy Bible API has the lower median latency in our checks — Holy Bible API responds in 852 ms versus Wolne Lektury at 1145 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 Holy Bible API and Wolne Lektury need an API key?

Neither needs a paid key — Holy Bible API is callable with no signup, and Wolne Lektury is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Holy Bible API and Wolne Lektury from the browser?

Only Wolne Lektury is browser-friendly — it returns CORS headers over HTTPS. Holy Bible API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Holy Bible API and Wolne Lektury free for commercial use?

Holy Bible API has unclear commercial terms, and Wolne Lektury 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.