API.Bible for AI agents
API.Bible provides Scripture text and audio across many translations for developers building Bible apps and study tools, covering passages, chapters, and full audio Bibles. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in API.Bible.
Look up a Bible passage
Retrieve a specific verse or passage from a chosen translation for a study tool.
Search Scripture by keyword
Search across a Bible version for verses matching a keyword or phrase.
Browse available translations
List the Bible versions supported before selecting one for a passage lookup.
19 API.Bible actions, graded by risk.
Every API.Bible action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
19Look things up. Allowed by default.
- api_bible.get_bookGet Book
- api_bible.get_bibleGet Bible by ID
- api_bible.get_verseGet Verse
- api_bible.get_chapterGet Chapter
- api_bible.get_passageGet Passage
- api_bible.get_sectionGet Section
- api_bible.list_versesList Verses
- api_bible.get_sectionsGet Sections
- api_bible.get_all_booksGet All Books
- api_bible.list_chaptersList Chapters
- api_bible.search_versesSearch Bible Verses
- api_bible.get_audio_bookGet Audio Book
- api_bible.get_audio_bibleGet Audio Bible by ID
- api_bible.list_audio_booksList Audio Books
- api_bible.get_audio_chapterGet Audio Chapter
- api_bible.list_audio_biblesList Audio Bibles
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
API.Bible in three steps.
- 01Your users connect API.BibleThey add their API.Bible api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls API.Bible through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('api_bible', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How API.Bible connects.
Users add their API.Bible api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same API.Bible connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use API.Bible from any agent.
API.Bible and Arc0, answered.
Can I use API.Bible with Claude, ChatGPT or Cursor?
Yes. Connect API.Bible to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the API.Bible actions you allow.
How do users connect API.Bible?
Users add their API.Bible api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which API.Bible actions can my agent take?
19 in total: 19 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in API.Bible?
Yes. Allow read actions and deny writes in the API.Bible policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call API.Bible too?
Yes. The same API.Bible connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug API.Bible into your agent.
Your users connect API.Bible once, under your brand. Your agent gets 19 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan