shipapis
StarSubmit an APISubmit API

Crossref Metadata Search vs Holy Bible API

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

APICrossref Metadata SearchHEALTHY90Holy Bible APIHEALTHY88
Uptime · 30d
Uptime · 90d97.1%100%
Uptime · 30d95.0%100%
P50 · ms522852
P95 · ms26832274
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseOpen Crossref metadata (much is CC0)Unverified
Free tierFree, no key (public pool)Free — limits not published
Rate limit5 requests/second, 1 concurrent (public pool, per X-Rate-Limit headers)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Crossref Metadata Search vs Holy Bible API: common questions

Which is more reliable, Crossref Metadata Search or Holy Bible API?

On our scheduled checks, Holy Bible API leads on measured uptime — Crossref Metadata Search at 97.1% 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, Crossref Metadata Search or Holy Bible API?

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

Neither needs a paid key — Crossref Metadata Search 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 Crossref Metadata Search and Holy Bible API from the browser?

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

Crossref Metadata Search allows commercial use on its free tier, 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.