shipapis
StarSubmit an APISubmit API

Holy Bible API vs Wiktionary

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

APIHoly Bible APINEW—WiktionaryNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedContent under CC BY-SA 4.0 / GFDL
Free tierFree — limits not publishedFree — public MediaWiki action API
Rate limitUnpublishedNo hard published cap; Wikimedia User-Agent policy and request-etiquette apply
In directory since2026-07-052026-07-05
operationalpartialdownno data

Holy Bible API vs Wiktionary: common questions

Which is more reliable, Holy Bible API or Wiktionary?

On our scheduled checks, Wiktionary leads on measured uptime — Holy Bible API at —% versus Wiktionary 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 Holy Bible API and Wiktionary need an API key?

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

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

Only Holy Bible API is browser-friendly — it returns CORS headers over HTTPS. Wiktionary needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Holy Bible API and Wiktionary free for commercial use?

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