shipapis
StarSubmit an APISubmit API

Quran vs Wiktionary

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

APIQuranHEALTHY100WiktionaryHEALTHY88
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms26542
P95 · ms6944709
Authnonenone
CORSyesno
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

Quran vs Wiktionary: common questions

Which is more reliable, Quran or Wiktionary?

On our scheduled checks, Quran leads on measured uptime — Quran 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, Quran or Wiktionary?

Quran has the lower median latency in our checks — Quran responds in 26 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 Quran and Wiktionary need an API key?

Neither needs a paid key — Quran 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 Quran and Wiktionary from the browser?

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

Quran 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.