API.Bible MCP integration for AI agents.
Connect AI agents to API.Bible through 8 structured actions, including get chapter, get passage, and get verse. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the API.Bible integration exposes
The API.Bible Agent App exposes 8 provider-backed actions for data work. Its current contract lets an authorized agent retrieve one chapter with configurable display options from api.bible, retrieve one passage with configurable display options from api.bible, and retrieve one verse with configurable display options from api.bible. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected API.Bible account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real API.Bible capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_chapterREADRetrieve one chapter with configurable display options from API.Bible.
INPUTS: bibleId / chapterId / parallels / contentType / includeNotes
get_passageREADRetrieve one passage with configurable display options from API.Bible.
INPUTS: bibleId / passageId / parallels / contentType / includeNotes
get_verseREADRetrieve one verse with configurable display options from API.Bible.
INPUTS: bibleId / verseId / parallels / contentType / includeNotes
list_biblesREADList Bible versions from API.Bible with optional language, abbreviation, or name filters.
INPUTS: language / abbreviation / name
list_booksREADList books for one Bible version from API.Bible.
INPUTS: bibleId
list_chaptersREADList chapters for one book in one Bible version from API.Bible.
INPUTS: bibleId / bookId
list_versesREADList verses for one chapter in one Bible version from API.Bible.
INPUTS: bibleId / chapterId
search_scriptureREADSearch scripture within one Bible version from API.Bible and preserve whether the result is verse-based or passage-based.
INPUTS: bibleId / query / limit / offset
INPUT CONTRACTS
Know what the action needs before it runs.
get_chapter
bibleIdREQUIRED- The Bible identifier used to retrieve the chapter.
chapterIdREQUIRED- The chapter identifier used to retrieve the chapter.
parallelsOPTIONAL- A comma-separated list of Bible identifiers used for parallel content comparison.
contentTypeOPTIONAL- The content format requested from API.Bible.
includeNotesOPTIONAL- Whether to include footnotes in the returned content.
get_passage
bibleIdREQUIRED- The Bible identifier used to retrieve the passage.
passageIdREQUIRED- The passage identifier used to retrieve the passage.
parallelsOPTIONAL- A comma-separated list of Bible identifiers used for parallel content comparison.
contentTypeOPTIONAL- The content format requested from API.Bible.
includeNotesOPTIONAL- Whether to include footnotes in the returned content.
get_verse
bibleIdREQUIRED- The Bible identifier used to retrieve the verse.
verseIdREQUIRED- The verse identifier used to retrieve the verse.
parallelsOPTIONAL- A comma-separated list of Bible identifiers used for parallel content comparison.
contentTypeOPTIONAL- The content format requested from API.Bible.
includeNotesOPTIONAL- Whether to include footnotes in the returned content.
list_bibles
languageOPTIONAL- The ISO language code used to filter Bible versions.
abbreviationOPTIONAL- The Bible abbreviation used to filter Bible versions.
nameOPTIONAL- The Bible name filter used to narrow the result set.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Chapter
Retrieve one chapter with configurable display options from API.Bible. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_chapterVerify with Get Passage
Retrieve one passage with configurable display options from API.Bible. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_passageSAFETY BOUNDARY
Operate API.Bible with explicit limits
- Authorize API.Bible with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned API.Bible data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in API.Bible rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the API.Bible task completed successfully.
CONNECTION MODEL
API key
API.Bible API key sent with the api-key request header. After approval, copy it from your credentials page: https://scripture.api.bible/admin/applications
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by API.Bible.