Holy Bible API vs PoetryDB

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

Uptime · 30d
Uptime · 90d100%86.3%
Uptime · 30d100%83.3%
P50 · ms852866
P95 · ms22743574
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (public-domain poetry; project is MIT-licensed)
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Holy Bible API vs PoetryDB: common questions

Which is more reliable, Holy Bible API or PoetryDB?

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

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

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

Can I call Holy Bible API and PoetryDB from the browser?

Only PoetryDB 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 PoetryDB free for commercial use?

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