shipapis
StarSubmit an APISubmit API

Kanji API vs Bible-api

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

APIKanji APIUNMONITORED—Bible-apiNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedPublic Domain (WEB translation; per translation_note in response)
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Kanji API vs Bible-api: common questions

Which is more reliable, Kanji API or Bible-api?

Only Bible-api is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Kanji API and Bible-api need an API key?

Neither needs a paid key — Kanji API 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 Kanji API and Bible-api from the browser?

Yes — both Kanji API and Bible-api 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 Kanji API and Bible-api free for commercial use?

Kanji API has unclear commercial terms, 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.