Holy Bible API vs Wiktionary

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms852542
P95 · ms22744709
Authnonenone
CORSnono
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, Holy Bible API leads on measured uptime — Holy Bible API at 100% versus Wiktionary at 99.02% 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 Wiktionary?

Wiktionary has the lower median latency in our checks — Holy Bible API responds in 852 ms versus Wiktionary at 542 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 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?

Neither sends browser-friendly CORS headers reliably, so call Holy Bible API and Wiktionary from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

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.