ScriptureFlow Developer Docs • AI / LLM Integration

Using ScriptureFlow with AI

Practical guidance for AI coding assistants, agents, and LLM-powered applications that need trustworthy multilingual Scripture retrieval.

← Back to Developer Docs home OpenAPI 3.1 Postman Collection

What ScriptureFlow is

ScriptureFlow is a public developer preview API and data layer for structured multilingual Scripture. It helps applications retrieve translation-aware, referenceable Scripture data without asking a language model to reproduce verse text from memory.

Use AI to choose tools, structure workflows, and explain results. Use ScriptureFlow—not generated model text—as the source for Scripture quotations.

How AI tools should discover translations

  1. Fetch /translations.json at runtime.
  2. Use the published version key exactly as returned, such as en-kjv.
  3. Check the public catalog and translation metadata before assuming complete coverage.
  4. Never silently switch to a different translation. Ask the user before substituting an unavailable version.

How AI tools should retrieve Scripture text

Use /api/verse for a requested verse or same-chapter passage. Use /api/quick-verse when the product needs a runtime-selected verse. Use /{version}/random.json for the generated, translation-scoped Verse of the Day.

Example API requests

Specific verse

GET https://scriptureflow-api-preview.pages.dev/api/verse?version=en-kjv&reference=John%203%3A16

Same-chapter passage

GET https://scriptureflow-api-preview.pages.dev/api/verse?version=en-kjv&book=Amos&chapter=8&verse=4&end_verse=6

Runtime-selected verse

GET https://scriptureflow-api-preview.pages.dev/api/quick-verse?version=en-kjv

Safe usage rules

  • Return Scripture text from the API response unchanged; do not invent, repair, or paraphrase missing text.
  • Separate Scripture text from generated commentary, summaries, applications, and devotional content.
  • Handle lookup errors explicitly instead of filling gaps from model memory.
  • Respect translation-specific canon, book availability, chapter divisions, and verse numbering.
  • Check /status.json because this is a developer preview.
  • Do not add theological interpretation or doctrinal labels to data represented as ScriptureFlow output.

Attribution guidance

Preserve the version key and translation name with user-facing Scripture text. Also preserve copyright, license, and attribution notices when supplied. Technical API availability does not automatically grant redistribution or commercial publication rights.

Reference: John 3:16
Translation: King James Version
Version key: en-kjv
Source: ScriptureFlow API

Example prompts for AI-assisted developers

Build a verse lookup form using ScriptureFlow. Fetch /translations.json first, use the selected version key exactly, call /api/verse, and display API errors without inventing verse text.
Add a “Quick Verse” button using /api/quick-verse?version=en-kjv. Label the translation and keep any generated reflection in a separate section below the returned Scripture text.
Generate a typed client from ScriptureFlow's OpenAPI 3.1 spec, then add tests for invalid versions, missing verses, and same-chapter passage ranges.

Mistakes to avoid

  • Guessing version keys such as kjv instead of discovering en-kjv.
  • Presenting model-generated wording as a direct Scripture quotation.
  • Silently substituting a translation when the requested version is unavailable.
  • Mixing commentary into the Scripture text field or quotation block.
  • Treating /{version}/random.json as a new random selection on every refresh.
  • Assuming all translations have identical coverage or canon.

Integration resources