Skip to content
Logos AI Logos AI Docs

Bring Your Own Key

Why BYOK exists

Section titled “Why BYOK exists”

BYOK keeps the power-user path open.

It gives you:

  • direct control over your own API usage
  • a cleaner cost story for advanced users
  • the option to combine API.Bible with local AI through Ollama

Core environment variables

Section titled “Core environment variables”
Terminal window
API_BIBLE_KEY=your_api_bible_key_here
OLLAMA_HOST=http://127.0.0.1:11434

For the browser reader:

Terminal window
PUBLIC_API_BIBLE_KEY=your_public_browser_key
PUBLIC_LOGOS_API_BASE=http://localhost:8484/api
Section titled “Recommended split”

Use this mental model:

  • desktop + CLI: API_BIBLE_KEY and local Ollama
  • browser reader: PUBLIC_API_BIBLE_KEY for direct static use, or PUBLIC_LOGOS_API_BASE for a backend proxy
  • managed future tier: no key setup for the end user

Local .env example

Section titled “Local .env example”
Terminal window
API_BIBLE_KEY=your_api_bible_key_here
OLLAMA_HOST=http://127.0.0.1:11434
PUBLIC_API_BIBLE_KEY=your_public_browser_key
PUBLIC_LOGOS_API_BASE=http://localhost:8484/api

Keep private variables out of source control. The PUBLIC_ values are intentionally different because Astro bakes them into the client build.