shipapis
StarSubmit an APISubmit API

Bible-api vs Holy Bible API

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

APIBible-apiHEALTHY93Holy Bible APIHEALTHY91
Uptime · 30d
Uptime · 90d98.9%100%
Uptime · 30d98.3%100%
P50 · ms328605
P95 · ms27961397
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licensePublic Domain (WEB translation; per translation_note in response)Unverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bible-api vs Holy Bible API: common questions

Which is more reliable, Bible-api or Holy Bible API?

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

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

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

Can I call Bible-api and Holy Bible API from the browser?

Only Bible-api 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 Bible-api and Holy Bible API free for commercial use?

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