Chinese Text Project vs Holy Bible API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree (higher limits with a free API key)Free — limits not published
Rate limitFair-use; raised with an API keyUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Chinese Text Project vs Holy Bible API: common questions

Which is more reliable, Chinese Text Project or Holy Bible API?

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

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

Can I call Chinese Text Project and Holy Bible API from the browser?

Yes — both Chinese Text Project and Holy 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 Chinese Text Project and Holy Bible API free for commercial use?

Chinese Text Project has unclear commercial terms, and Holy 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.