Bosca / Bible

Bosca Bible

Scripture,
structured and exact.

Every book, chapter, and verse is addressable content — many translations, language-aware, imported from the standard Paratext and USX bundles you already use, and served exactly as written, to your app or an AI agent alike.

How it works

Import, address, serve.

01

Import

Upload a translation as a standard USX bundle. The compiler reads the Paratext manifest and files and turns them into books, chapters, and verses you can address.

02

Address

Every verse has a canonical reference, so "John 3:16" resolves to exact content — a single verse, a range, or a whole chapter, with footnotes and styling intact.

03

Serve

Read scripture over GraphQL or REST, language-aware and permission-controlled — and hand the very same text to AI agents, which quote it rather than invent it.

What makes it powerful

Scripture as real, structured content

Not a wall of text — books, chapters, and verses you can address, translate, import, govern, and serve like everything else on the platform.

Books, chapters, verses

A Bible is structured content — the canonical books plus the deuterocanon, each chapter a tree of verses, footnotes, and styling.

Many translations

Hold as many translations as you like, each with its own names, abbreviations, and language.

Language-aware

Ask for a Bible and get the right translation for the reader's language — scripts and right-to-left included.

Real references

Parse "John 3:16" or "Genesis 1:1–5" into canonical USFM, resolve ranges, and pull exactly those verses.

Import from Paratext

Bring a translation as a standard USX bundle; the compiler turns the Paratext manifest and files into addressable scripture.

Quoted, never invented

AI agents read scripture through tools that return the real text of the installed translation — the model never makes a verse up.

Governed like any content

Scripture served by Bosca, so the same permissions, versions, and workflow states apply to it.

One API, two shapes

Reach any book, chapter, or reference over GraphQL or a plain REST endpoint.

Exact, by design

The text is the text

Scripture demands to be exact, so nothing paraphrases it. What you import is what you serve — and when an AI agent needs a verse, it calls a tool that returns the real text of the installed translation. The model plans and then uses the exact text; it never sources the words itself.

  • Agents list translations, look up books, resolve references, and fetch verses — all against the real Bible.
  • The language model is never the source of a verse; the installed translation is.
  • What you imported is served back unchanged, footnotes and styling included.
agent · tool call
bible_get_verses"John 3:16"

For God so loved the world…

read from WEB · not generated

Scripture, as a first-class citizen

Structured, multilingual, importable, and governed like all your other content — reachable by your apps, your references, and your agents, and always served exactly as written.