# API.Bible AI integration on Definable

> API.Bible allows developers to integrate Scripture content into their applications or websites for non-commercial purposes.

## What this connects

API.Bible allows developers to integrate Scripture content into their applications or websites for non-commercial purposes.

Vendor: https://scripture.api.bible/

## Tools available

**19** tools available. First 12:

- `API_BIBLE_GET_ALL_BOOKS` — Get All Books — Retrieve all books for a specific Bible version. Requires a valid Bible version ID (obtainable from Get Supported Versions). Returns a list of books with their IDs, names, and abbreviations in the Bible's native language.
- `API_BIBLE_GET_AUDIO_BIBLE` — Get Audio Bible by ID — Tool to retrieve details of a specific audio Bible by its ID. Use when you need metadata about an audio Bible version.
- `API_BIBLE_GET_AUDIO_BOOK` — Get Audio Book — Tool to retrieve a single audio Book object for a given audio Bible ID and book ID. Use when you need metadata about a specific audio book.
- `API_BIBLE_GET_AUDIO_CHAPTER` — Get Audio Chapter — Tool to retrieve a single audio chapter with mp3 resource URL. Use when you need to fetch audio content for a specific chapter of an audio Bible. The resourceUrl provided in the response is temporary and expires after a certain time (indicated by expiresAt).
- `API_BIBLE_GET_BIBLE` — Get Bible by ID — Tool to retrieve details of a specific Bible version by its ID. Use when you need full metadata after listing versions. Example prompt: 'Get metadata for bibleId de4e12af7f28f599-01'.
- `API_BIBLE_GET_BOOK` — Get Book — Tool to retrieve a single Book object for a given Bible version and book ID. Use when you need details about a specific book, optionally including its chapters.
- `API_BIBLE_GET_CHAPTER` — Get Chapter — Retrieve a complete chapter with all verses from a Bible version. Use when you need to fetch an entire chapter's content including all verses, navigation to adjacent chapters, and copyright information. First use Get Supported Versions to obtain valid Bible IDs.
- `API_BIBLE_GET_PASSAGE` — Get Passage — Retrieve a Bible passage by ID. A passage can represent a chapter, verse, or range of verses. Use when you need to fetch specific scripture content with configurable display options.
- `API_BIBLE_GET_SECTION` — Get Section — Retrieve detailed content for a Bible section by ID. A section represents a thematic grouping of verses (e.g., 'The Genealogy of Jesus', 'The Sermon on the Mount'). First use Get Sections to obtain section IDs for a specific book, then use this action to fetch the full content with configurable display options.
- `API_BIBLE_GET_SECTIONS` — Get Sections — Tool to retrieve a list of sections for a specific book in a Bible version. Use after obtaining the Bible and book IDs to view sectional breakdown.
- `API_BIBLE_GET_SUPPORTED_VERSIONS` — Get Supported Bible Versions — Retrieve a list of available Bible versions (translations) from API.Bible. Use this tool to: - List all available Bible translations before searching for verses - Find Bible versions by language (e.g., English, Spanish, German) - Search for specific translations by name or abbreviation - Get the Bible version ID needed for other API.Bible operations The returned version IDs can be used with other API.Bible tools to access specific Bible content like books, chapters, verses, and sections.
- `API_BIBLE_GET_VERSE` — Get Verse — Retrieve a specific Bible verse by ID. Use this action when you need to fetch the content of a single verse from a specific Bible version. First use Get Supported Versions to obtain a valid bibleId, then provide the verse ID in format BOOK.CHAPTER.VERSE (e.g., 'JHN.3.16' for John 3:16). Configurable display options allow control over footnotes, titles, and verse numbering.

## Auth

Auth schemes: `API_KEY`.

## How agents use API.Bible

Inside a Definable workflow, API.Bible is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → API.Bible** — the Researcher (GPT-5.5) pulls context from API.Bible (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → API.Bible** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into API.Bible (create record, post message, draft email).
- **Designer / Engineer → Distributor → API.Bible** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via API.Bible (attach file, open PR comment, post status).

The Verifier checks every API.Bible call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/api_bible/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt