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.

Developer toolsAPI keyMCP + RESTscripture.api.bible
AUDIT LOG · API.BIBLEPOLICY: acme-support
09:41:07 · claude · u_8f2read
api_bible.list_verses
List Verses✓ allowed · 212ms
09:41:08 · claude · u_8f2read
api_bible.get_book
Get Book✓ allowed · 164ms
EVERY API.BIBLE CALL, ON THE RECORD
01 · USE CASES

What agents do in API.Bible.

01

Look up a Bible passage

Retrieve a specific verse or passage from a chosen translation for a study tool.

02

Search Scripture by keyword

Search across a Bible version for verses matching a keyword or phrase.

03

Browse available translations

List the Bible versions supported before selecting one for a passage lookup.

02 · ACTIONS

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

19

Look things up. Allowed by default.

  • api_bible.get_book
    Get Book
  • api_bible.get_bible
    Get Bible by ID
  • api_bible.get_verse
    Get Verse
  • api_bible.get_chapter
    Get Chapter
  • api_bible.get_passage
    Get Passage
  • api_bible.get_section
    Get Section
  • api_bible.list_verses
    List Verses
  • api_bible.get_sections
    Get Sections
  • api_bible.get_all_books
    Get All Books
  • api_bible.list_chapters
    List Chapters
  • api_bible.search_verses
    Search Bible Verses
  • api_bible.get_audio_book
    Get Audio Book
  • api_bible.get_audio_bible
    Get Audio Bible by ID
  • api_bible.list_audio_books
    List Audio Books
  • api_bible.get_audio_chapter
    Get Audio Chapter
  • api_bible.list_audio_bibles
    List Audio Bibles
+ 3 MORE

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

API.Bible in three steps.

  1. 01Your users connect API.BibleThey add their API.Bible api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 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.
POLICY.TS
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
04 · AUTH AND DATA

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
05 · WORKS WITH

Use API.Bible from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

API.Bible and Arc0, answered.

Q01

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.

Q02

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.

Q03

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.

Q04

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.

Q05

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.

Get started

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