Quran vs Quran-api

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms27650
P95 · ms6943715
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no key (static CDN JSON files)
Rate limitUnpublishedNone (served as static files from jsDelivr CDN)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Quran vs Quran-api: common questions

Which is more reliable, Quran or Quran-api?

Both are neck-and-neck — Quran and Quran-api each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Quran or Quran-api?

Quran has the lower median latency in our checks — Quran responds in 27 ms versus Quran-api at 650 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 Quran and Quran-api need an API key?

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

Can I call Quran and Quran-api from the browser?

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

Quran has unclear commercial terms, and Quran-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.