shipapis
StarSubmit an APISubmit API

Bible-api vs PoetryDB

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

APIBible-apiHEALTHY92PoetryDBHEALTHY78
Uptime · 30d
Uptime · 90d100%86.3%
Uptime · 30d100%83.3%
P50 · ms604866
P95 · ms27963574
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licensePublic Domain (WEB translation; per translation_note in response)Unverified (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

Bible-api vs PoetryDB: common questions

Which is more reliable, Bible-api or PoetryDB?

On our scheduled checks, Bible-api leads on measured uptime — 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, Bible-api or PoetryDB?

Bible-api has the lower median latency in our checks — Bible-api responds in 604 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 Bible-api and PoetryDB need an API key?

Neither needs a paid key — 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 Bible-api and PoetryDB from the browser?

Yes — both Bible-api and PoetryDB 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 Bible-api and PoetryDB free for commercial use?

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.