Skip to content
Logos AI Logos AI Docs

API.Bible Key

What you need

Section titled “What you need”

Logos AI uses API_BIBLE_KEY for desktop, CLI, and backend workflows.

The browser reader can also use a public build-time key through PUBLIC_API_BIBLE_KEY when you are comfortable exposing it in the client bundle.

Create the key

Section titled “Create the key”

These steps are based on the current official API.Bible flow:

  1. Register as a developer: docs.api.bible/getting-started/setup-an-account
  2. Create an app: docs.api.bible/getting-started/setup-an-app
  3. Review the authentication guide: docs.api.bible/getting-started/authentication

Useful official entry points:

Once the app is approved, API.Bible exposes the key through your dashboard settings.

Desktop and CLI setup

Section titled “Desktop and CLI setup”

Put the key in a local environment file or shell profile:

Terminal window
API_BIBLE_KEY=your_api_bible_key_here

For local desktop and CLI use, keep that key out of git.

Section titled “Paid setup help and future premium path”

If you do not want to work through the API.Bible dashboard yourself, guided setup can also be handled as a paid setup-help option.

For now, the normal path is still a user-managed key. A future premium edition may instead use a commercial managed key once that cost is part of the paid offering.

Browser reader setup

Section titled “Browser reader setup”

If you want the static Astro web reader to call API.Bible directly from the browser, use:

Terminal window
PUBLIC_API_BIBLE_KEY=your_public_browser_key

That is fine when you are intentionally comfortable with the key being public in the built site.

Backend proxy option

Section titled “Backend proxy option”

If you want the web experience to call an existing Logos backend instead of API.Bible directly, use:

Terminal window
PUBLIC_LOGOS_API_BASE=http://localhost:8484/api

That lets the browser talk to your own API surface instead of the third-party service directly.