BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.

bilingual_book_maker

CLI that translates EPUB/TXT/SRT/PDF books into bilingual editions using your own LLM key.

Category:: Productivity Tools
Maintenance:: Actively developed (last commit today)
Pricing:: Open Source
Open source:: Yes (MIT)
Self-hostable:: Yes
Local-first:: Yes
Platforms:: CLI, Self-hosted, Docker
AI providers (bring your own key):: OpenAI, Anthropic, Google Gemini, Azure OpenAI, Groq, xAI Grok, DeepSeek, Ollama, Custom / OpenAI-compatible
API key storage:: Configured by environment variable
Key risk level:: LOW
Trust score:: 93/100

An open-source Python command-line tool that converts EPUB, TXT, MD, SRT, and PDF files into bilingual (side-by-side) editions by translating them with an LLM or translation engine of your choice. The end user supplies their own API key per provider via dedicated CLI flags and BBM_* environment variables: --openai_key/BBM_OPENAI_API_KEY for OpenAI, --claude_key/BBM_CLAUDE_API_KEY for Anthropic Claude, --gemini_key/BBM_GOOGLE_GEMINI_KEY for Google Gemini, --groq_key/BBM_GROQ_API_KEY for Groq, --xai_key/BBM_XAI_API_KEY for xAI Grok, --deepl_key/BBM_DEEPL_API_KEY for DeepL, --qwen_key for Qwen, plus --api_key combined with --provider for any custom OpenAI-compatible endpoint. Ollama is supported for fully local/self-hosted models, and free engines (Google Translate, DeepL Free) are also available. Installed via pip (pip install -U bbook_maker) and run as the bbook CLI or python3 make_book.py. MIT-licensed, ~9.3k GitHub stars, actively maintained (latest release v1.1.0, July 2025), Python 3.10+.

Why this trust score (93/100)

Trust measures how the tool treats your API key and how much of that has been verified. It contains no popularity signal.

Key Safety 22/25: The key is supplied by an environment variable or local config file you control.
Request Routing 20/20: Requests go straight from you to the AI provider. The provider endpoint is configurable, so you can point it at the provider or your own gateway.
Transparency 20/20: Source is public under MIT, so anyone can check how the key is handled. Key handling was located in the published source.
Privacy 14/15: Local-first: it works without sending your data anywhere. Can be self-hosted, so the data path stays inside infrastructure you control.
Maintenance 10/10: Actively developed: commits within the last three months.
Verification Confidence 7/10: Key handling was found in the published source by BYOAIK's scanner.

What was checked

Verification tier SOURCE_VERIFIED, derived from the evidence below and not set by hand.

[REPORTED · RESEARCH] This listing was compiled by an AI-assisted research pass over the tool's public website, README and documentation. No person independently confirmed it.
[STRONG · SOURCE_SCAN] The user supplies their own OpenAI key: the project references its API key variable. source
[STRONG · SOURCE_SCAN] Supports a local model backend, so it can run with no cloud provider key at all. source
[STRONG · SOURCE_SCAN] The provider endpoint is configurable, so requests can be pointed straight at the provider or at your own gateway. source
[CONFIRMED · SOURCE_SCAN] Ships a container definition, so it can be self-hosted on your own infrastructure. source
[CONFIRMED · SOURCE_SCAN] Most recent commit 2026-08-14, about 0 month(s) ago. source

How your API key is handled

Your API key is supplied via an environment variable or local config file. Requests are sent directly to the AI provider. Because it can be self-hosted, your key never has to touch a third-party backend.

Setup

Install the tool, set your provider API key as an environment variable (or in its config file), and pick a model.