Live verse text is fetched when a resolvable reference is found (including chapter-only asks such as Psalm 136 or John 1). Topical answers may still use the model; use the Sources line under a reply to verify what was fetched.
AI chat requires a free account (7-day trial or invite-only 14-day tester access). The Bible reader at /read is always free.
Bible Scripture Text (English + Original Languages)
- Live from the network — not written into the code or baked into the model. All text (English and originals) is fetched on-demand from the public Free Use Bible API at https://bible.helloao.org.
- When you mention a reference (e.g. "Galatians 6", "John 1:1-5", or ask about a Greek/Hebrew word), the server detects it and fetches the exact verses.
- English grounding: Berean Standard Bible (BSB) is the default. User-selectable in Settings: BSB, KJV, NET, Darby, ASV, YLT, or WEB — all fetched live from bible.helloao.org only.
- Greek New Testament: SBL Greek New Testament is fetched by default with English when a New Testament reference resolves. Byzantine Greek NT or Textus Receptus are fetched only when you name them (for example “the TR” or “Byzantine”).
- Hebrew Old Testament: Westminster Leningrad Codex (WLC / hbo_wlc) is fetched by default for Old Testament references. John cites that edition when a live Hebrew block was loaded.
- After the AI replies, the server scans the reply for any scripture the model referenced and fetches accurate live text (English + original where available) for the sources panel.
- John is instructed to name the edition that was actually fetched (SBL Greek New Testament or Westminster Leningrad Codex by default), to lead with transliteration for speech, and not to present guessed Greek or Hebrew letters as live text.
What "Context" Means in This App
"Context" is the disciplined practice of letting The Word interpret The Word — and of reading each passage as the product of a real author writing at a real time in the history of revelation, not as floating words with no writer or date. It includes:
- Author & composition: Who wrote this book (as The Word claims, or by historic church attribution), to whom, and approximately when relative to other books. You cannot treat Matthew, Mark, Luke, and Paul as if they all wrote at the same moment.
- Writing order: Earlier books and later books stand in a real sequence. Default for the Gospels in this app: Matthew first, then Mark, then Luke, then John (Acts with Luke). Letters and Prophets likewise sit in a progressive timeline of revelation.
- Literary context: The immediate sentence, paragraph, chapter, and book — how the words function in the author's flow of argument or story.
- Grammatical & syntactic context: In the original Greek or Hebrew, verb tense, voice, mood, word order, case, and sentence structure often carry nuances that translations can only approximate.
- Lexical context: How the same Greek or Hebrew word is used by this author elsewhere, in the same book, then in the wider canon — not from later extra-biblical writings.
- Historical context of the biblical text: language, audience, genre, and setting recovered from the passage and the rest of Scripture — not from Josephus, Philo, church fathers, the Talmud, or other extra-biblical writings.
- Canonical context: How the passage relates to the rest of Scripture and the overall redemptive story — always respecting who wrote each witness and in what order.
How to Understand Greek & Hebrew in Context (the Process)
- Begin with the literal text supplied by the app (SBL Greek New Testament for the NT; Westminster Leningrad Codex for the Hebrew OT).
- Name the author and place the book in relative composition order before drawing conclusions from parallels.
- Read the surrounding verses and chapters to grasp the author's immediate purpose and audience.
- Identify significant words or constructions and study their usage in the original language (the app surfaces these when you ask about a specific term).
- Analyze the grammar: Who is acting? What is the tense, aspect, or emphasis? How does the sentence structure shape meaning?
- Consider genre (narrative, poetry, epistle, prophecy, etc.) because different genres use language differently.
- Compare the same words, themes, or constructions elsewhere in the author's writings first, then the wider canon — noting which books were written earlier or later.
- Only after the text has spoken in its original context do we move to application or theology — always letting the particulars of the Greek or Hebrew, the author, and composition order guide us.
The system prompt given to Grok explicitly requires this contextual, original-language-first approach for every reference to The Word.
Citations You Hear When It Speaks
Spoken answers name the English translation and the original edition that was fetched. You hear transliteration (for example “ho logos” or “chesed”). Greek or Hebrew letters stay on screen and in Sources unless you ask John to pronounce them.
“John 1:1 according to the Berean Standard Bible… In the SBL Greek New Testament, en archē ēn ho logos (Ἐν ἀρχῇ ἦν ὁ λόγος).”
“Psalm 136:1 in the Westminster Leningrad Codex: ki le-olam chasdo (כִּי לְעוֹלָם חַסְדּוֹ).”
AI Model
- Responses generated by Grok 4.3 (model: grok-4.3).
- Calls go through a secure server-side proxy — your xAI API key never leaves the server and is never exposed to the browser.
Voice (Text-to-Speech)
- Browser voices only (window.speechSynthesis). iPhone: basic system voices only (any browser) — try Daniel or Karen. Mac: Chrome for Enhanced voices from Spoken Content. No app filter.
- No server TTS, no xAI voices, no cloud voices for speech output. All speaking (manual replies, auto-speak, hands-free, preview tests) uses only your device's own voices.
Conversation History
Your chats are stored only in your browser’s localStorage (they survive refresh but stay on this device).
This design lets you verify every reference to The Word against the actual source. The Bible data comes from the open public API at bible.helloao.org.
Full translation copyright notices: Copyright & Attributions.