shipapis
StarSubmit an APISubmit API

Bible-api vs Crossref Metadata Search

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

APIBible-apiNEW—Crossref Metadata SearchNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licensePublic Domain (WEB translation; per translation_note in response)Open Crossref metadata (much is CC0)
Free tierFree — limits not publishedFree, no key (public pool)
Rate limitUnpublished5 requests/second, 1 concurrent (public pool, per X-Rate-Limit headers)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bible-api vs Crossref Metadata Search: common questions

Which is more reliable, Bible-api or Crossref Metadata Search?

On our scheduled checks, Crossref Metadata Search leads on measured uptime — Bible-api at —% versus Crossref Metadata Search at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Bible-api and Crossref Metadata Search need an API key?

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

Can I call Bible-api and Crossref Metadata Search from the browser?

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

Bible-api has unclear commercial terms, and Crossref Metadata Search allows commercial use on its free tier. 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.