Abibliadigital A Bíblia Digital API

Name: A Bíblia Digital 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.

Install Jentic One Beta

Connect the A Bíblia Digital API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the A Bíblia Digital API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with A Bíblia Digital 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

GET STARTED

Start building with A Bíblia Digital API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use A Bíblia Digital 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 your Jentic One instance. 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 Jentic?

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

Credential isolation

Your A Bíblia Digital API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'fetch a Bible verse' or 'search the scripture text', and Jentic returns the matching A Bíblia Digital operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using A Bíblia Digital 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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the A Bíblia Digital API?

Yes. Because you run Jentic One yourself, your own rules decide which A Bíblia Digital operations and credentials the agent may use, and this API is read-only, so nothing it does can change data. You choose which of the five read calls the agent may run, for example allowing GET /verses/{version}/{book}/{chapter}/{verse} and GET /search while withholding the others. Since the version, book, chapter, and verse all sit in the URL path, a rule can pin the agent to a specific version or passage rather than the whole Bible.