PoetryDB vs Quran-api

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

Uptime · 30d
Uptime · 90d86.3%100%
Uptime · 30d83.3%100%
P50 · ms866650
P95 · ms35743715
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (public-domain poetry; project is MIT-licensed)Unverified
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

PoetryDB vs Quran-api: common questions

Which is more reliable, PoetryDB or Quran-api?

On our scheduled checks, Quran-api leads on measured uptime — PoetryDB at 86.3% versus Quran-api at 100% 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, PoetryDB or Quran-api?

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

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

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

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