shipapis
StarSubmit an APISubmit API

Wiktionary vs Bible-api

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

APIWiktionaryNEW—Bible-apiNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseContent under CC BY-SA 4.0 / GFDLPublic Domain (WEB translation; per translation_note in response)
Free tierFree — public MediaWiki action APIFree — limits not published
Rate limitNo hard published cap; Wikimedia User-Agent policy and request-etiquette applyUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Wiktionary vs Bible-api: common questions

Which is more reliable, Wiktionary or Bible-api?

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

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

Can I call Wiktionary and Bible-api from the browser?

Only 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 Wiktionary and Bible-api free for commercial use?

Wiktionary allows commercial use on its free tier, and 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.