A Bíblia Digital API

Name: A Bíblia Digital API API
Brand: A Bíblia Digital API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey5 EndpointsREST

For Agents

Look up Bible books, chapters, verses, and run keyword search across seven Bible versions in four languages. Read-only API gated by an API key.

Quickstart

Get started with A Bíblia Digital API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"fetch a Bible verse"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with A Bíblia Digital API API.

List every book of the Bible with metadata such as testament and chapter count

Retrieve a single book by abbreviation

Fetch all verses in a chapter for a chosen Bible version

Pull a single verse in a chosen version

Run a keyword search across the text and return matching verse references

GET STARTED

Start building with A Bíblia Digital API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for A Bíblia Digital API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for A Bíblia Digital API, keeping it validated and agent-ready. A Bíblia Digital is a RESTful Bible content API offering seven Bible versions across four languages, with endpoints for browsing books, fetching chapters and individual verses, and searching for keywords. The five-endpoint surface is small and read-only, gated by an API-key bearer scheme. It powers daily verse, devotional, and search features in religious apps without requiring local Bible text storage.

Use Cases

Patterns agents use A Bíblia Digital API API for, with concrete tasks.

★ Daily Verse Feature

Religious apps surface a daily verse on the home screen so users see fresh scripture each day. GET /verses/{version}/{book}/{chapter}/{verse} returns the chosen verse in the requested version, so a scheduler can rotate references over a year without bundling the Bible text into the app. The same endpoint backs share-card features that need a known reference fetched on demand.

Fetch the verse John 3:16 from the kjv version and return its text

Chapter Reading View

Reading apps render full chapters and let the user navigate book by book. GET /verses/{version}/{book}/{chapter} returns the verses for the chapter in one call, and GET /books with GET /books/{book} let the UI build navigation menus with the right chapter counts. The flat surface keeps the read path simple.

Fetch all verses in Psalms chapter 23 from the nvi version for the reading view

Keyword Search Across Scripture

Discovery features need fast keyword search across the Bible without indexing the text locally. GET /search returns matching references for a query string, so an app can show search results and link directly to the verse endpoint for the full text. This supports topical study, sermon prep, and chat-style lookup.

Search for 'forgiveness' in the kjv version and return the first 10 matching verse references

Agent-Driven Scripture Lookup via Jentic

Conversational AI agents commonly need to quote a verse or list passages on a topic. Through Jentic, an agent searches by intent, loads the matching verse or search operation from A Bíblia Digital, and executes the lookup with the API key held in the Jentic vault. The structured response slots straight into the agent's reply.

Search Jentic for 'fetch a Bible verse', load the abibliadigital schema, and execute the call for the requested reference

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for a bíblia digital api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/books

List all books of the Bible

GET

/books/{book}

Get a single book's metadata

GET

/verses/{version}/{book}/{chapter}

Get verses for a chapter

GET

/verses/{version}/{book}/{chapter}/{verse}

Get a single verse

GET

/search

Search for verses by keyword

GET

/books

List all books of the Bible

GET

/books/{book}

Get a single book's metadata

GET

/verses/{version}/{book}/{chapter}

Get verses for a chapter

GET

/verses/{version}/{book}/{chapter}/{verse}

Get a single verse

GET

/search

Search for verses by keyword

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

A Bíblia Digital API keys are stored encrypted in the Jentic vault. Agents call operations by ID and Jentic injects the Authorization header at execution time, so the raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'fetch a Bible verse') and Jentic returns the matching verse, chapter, or search operation along with its input schema.

Time to first call

Direct integration: a few hours to wire up auth and the read endpoints. Through Jentic: minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Bible-API

Open Bible API with passage and search endpoints in multiple translations.

Choose Bible-API for an open public-domain translation set; pick A Bíblia Digital for richer Portuguese coverage and seven versions in one surface.

Complementary

AB.GL

URL shortener for tracking shared scripture links.

Use AB.GL alongside A Bíblia Digital to shorten share links pointing to specific verses or chapters.

Complementary

8x8 Connect SMS

SMS API for sending verse-of-the-day or devotional messages.

Pair with 8x8 Connect to send daily verses fetched from A Bíblia Digital as SMS messages.

FAQs

Specific to using A Bíblia Digital API API through Jentic.

Why is there no official OpenAPI spec for A Bíblia Digital API?

abibliadigital.com.br publishes a docs page but not a discoverable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call A Bíblia Digital API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the A Bíblia Digital API use?

The API uses an API key passed in the request headers (apiKey scheme). Through Jentic, the key is stored encrypted in the Jentic vault and injected at execution time, so the agent never sees the raw key in its context.

Can I search the Bible text with the A Bíblia Digital API?

Yes. GET /search runs a keyword search and returns matching verse references in the chosen version. Pair the result with GET /verses/{version}/{book}/{chapter}/{verse} to fetch the full text for any reference returned by the search.

How do I fetch a specific verse through Jentic?

Search Jentic for 'fetch a Bible verse' to find GET /verses/{version}/{book}/{chapter}/{verse}, load the schema, and execute the call with the chosen version, book, chapter, and verse. Jentic returns the verse text ready to drop into the agent's reply.

Which Bible versions and languages are supported?

The API exposes seven versions across four languages, including English (KJV), Portuguese (NVI), and other widely used translations. Pass the version code in the path of the verse and chapter endpoints; GET /books returns the books available for navigation.

Is the A Bíblia Digital API free to use?

abibliadigital.com.br offers free access tiers with rate limiting plus higher-volume options on request. The OpenAPI spec does not encode tier limits; check the abibliadigital.com.br site for current pricing and quotas before high-traffic use.