Every āyah on AyaSeerah comes from a 100% verified public source
AyaSeerah does not store its own copy of the Qur'an as the thing you read. Arabic text and translation are fetched live, per āyah, from published and independently verifiable endpoints — and every verse is labelled with its verse key so you can check it yourself.
Quran.com API (v4)
Uthmānī script (KFGQPC lineage) + Ṣaḥīḥ International translation, fetched per āyah at read time.
Quran.com API (v4) — tajwīd script (text_uthmani_tajweed)
The same Uthmānī text, served with inline tajwīd rule annotations (madd, ghunnah, qalqalah, idghām, ikhfāʾ, iqlāb and the rest of the dataset's rule set). AyaSeerah only colours what the API marks — no tajwīd rules are detected or invented here, and the colour convention is the one the dataset itself specifies.
Quran.com / Quran Foundation Audio API (v4)
Ayah-by-ayah recitation audio (/recitations/{id}/by_chapter) with word-level segment timings. Verse-recitation IDs are kept strictly separate from the chapter-reciter ID space, as the API documents.
Tanzil Project
The verified Unicode Qur'an text standard that the served Uthmānī text descends from, checked against the Madinah Mushaf.
KFGQPC / Madinah Mushaf
The printed reference of record for Ḥafṣ ʿan ʿĀṣim orthography and āyah numbering.
Don't take our word for it — check an āyah right now
Trust in a Qur'an app should be verifiable, not asserted. This runs the same request the surah pages run.
VERIFY IT YOURSELF
Enter any verse key. Your browser calls the same public endpoint AyaSeerah calls — no AyaSeerah server in between. The request URL is shown so you can paste it into your own browser and compare.
How Qur'anic apps are tested for compliance — and how that applies here
There is no single global certification for Qur'an apps. In practice, compliance means two things: the Arabic text must be provably identical to a certified muṣḥaf, and the interpretive content must be attributable to named scholarship. Regional bodies — KFGQPC in Saudi Arabia, LPMQ in Indonesia — review muṣḥaf editions on exactly those grounds, and their criteria translate directly into automated tests.
- 01
Source-of-truth binding
Text and translation are never hand-typed. Each āyah is requested by verse key (e.g. 18:10) from the Quran.com v4 API, and the verse key is printed next to the āyah so any reader can verify it against the same endpoint.
- 02
Character-level diff against a reference text
The standard compliance test for Qur'anic software: normalise (NFC), strip presentation-only marks, and diff every āyah against the Tanzil Uthmānī text. Any non-zero diff fails the build. This is the method mushaf-review bodies (KFGQPC, Indonesia's LPMQ) apply to printed and digital muṣḥaf.
- 03
Checksum manifest
A per-āyah SHA-256 hash, rolled up to per-sūrah and whole-mushaf root hashes. Cached or bundled text is verified against the manifest before it is displayed, guarding against corrupted downloads or tampered copies.
- 04
Structural assertions
6,236 āyāt, 114 sūrahs, correct āyah counts per sūrah, basmalah handling (present except at-Tawbah, counted only in al-Fātiḥah), and sajdah markers in the right places. These are cheap automated tests that catch the majority of real-world Qur'an app defects.
- 05
Rendering & orthography checks
Right-to-left order, diacritic stacking, small alif and hamzat al-waṣl preserved, no line-break inside a word, and no autocorrect/font substitution — verified visually per device, because a correct string can still render wrongly.
- 06
Fail-safe behaviour
If the API is unreachable, AyaSeerah shows stored text explicitly labelled as such rather than silently degrading — and never invents, paraphrases or AI-generates a single word of Qur'anic text.
- 07
Tajwīd colouring is sourced, not computed
Tajwīd colours come from the API's own annotated script field, spot-checked against Quran.com's tajwīd view and a printed tajwīd muṣḥaf across a sample covering each rule type (madd, ghunnah, qalqalah, idghām with and without ghunnah, ikhfāʾ, iqlāb). Where the API returns no annotation for an āyah, the plain text is shown with a visible 'tajwīd markup unavailable' notice rather than uncoloured text presented as complete.
- 08
Human scholarly review
Automation proves the Arabic string is right; it cannot prove that a tafsīr summary is faithful. Every commentary note, asbāb al-nuzūl narration and takeaway names its classical source (Ibn Kathīr, al-Qurṭubī, al-Ṭabarī, aṭ-Ṭabarānī, Bukhārī/Muslim) so a qualified reader can audit it.
The protocol, scored honestly
Publishing a protocol is easy; claiming to have passed all of it would be dishonest. Here is what is live today and what is still to come.
Is there already an app like this?
There are excellent Qur'an apps — but they cluster into readers, ḥifẓ trainers, daily habit apps and video courses. None of them teaches the Qur'an in revelation order beside the seerah and then tests whether you retained it. That gap is what AyaSeerah occupies.
Comparison based on each product's publicly documented features at time of writing. Nothing here is a criticism of their scholarship — several are used daily by this project's own author.
Capability matrix
Where AyaSeerah is weaker, it says so — you should be using a recitation checker and a full mushaf reader alongside it.
Based on each product's publicly documented features at time of writing; features change, so verify before relying on this.
The questions a careful student should ask
Who reviewed the tafsīr content? Is it scholar-certified?
No — and AyaSeerah says so plainly rather than implying otherwise. The study content is a compilation, not an independent scholarly ruling. Its safeguard is attribution: every asbāb al-nuzūl narration, thematic reading and takeaway names the classical work it comes from (Ibn Kathīr, al-Ṭabarī, al-Qurṭubī, al-Saʿdī, and the ḥadīth collections), so a teacher or student can check it at the source. Study with a teacher; use this as the scaffolding between classes.
Is any Qur'anic text AI-generated or paraphrased?
Never. Arabic text and translation are fetched verbatim from the Quran.com API and rendered as returned. No model writes, completes, corrects or reformats a single word of Qur'an. AI is used in the app only for optional OCR of your own handwritten class notes.
What if the API is down or you go offline?
The page shows the stored study text with a visible label saying it is a fallback, not the live canonical fetch. It never fails silently and never substitutes an unverified string while presenting it as verified.
How is the revelation order decided — isn't that disputed?
Yes, and the app treats it as disputed. Each sūrah carries a certainty level: mutawātir/ṣaḥīḥ-attested placements (e.g. al-ʿAlaq first), strongly-reported placements, and reconstructions where scholars differ. Where the ordering is scholarly ijtihād (al-Suyūṭī's al-Itqān, Nöldeke-influenced tables, and the Egyptian standard order), that is stated on the phase, not hidden.
Can I report an error?
Yes, and please do. Text errors are checkable in seconds against the printed verse key; content errors are checkable against the cited source. Reported corrections take priority over new features.
Start where it's meant to start
The first revelation, in its historical moment, with its themes, roots and takeaways.
Open the curriculum