BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.
Summarize
Point at any URL, YouTube, podcast, PDF, or file and get the gist, via Chrome/Firefox sidebar or CLI using your own model API key.
- Category:
- Browser Extensions
- Maintenance:
- Actively developed (last commit today)
- Pricing:
- Open Source
- Open source:
- Yes (MIT)
- Self-hostable:
- Yes
- Local-first:
- Yes
- Platforms:
- Browser Extension, CLI, Self-hosted, Docker
- AI providers (bring your own key):
- OpenAI, Anthropic, Google Gemini, xAI Grok, OpenRouter, Ollama, Custom / OpenAI-compatible
- API key storage:
- Stored in browser storage
- Key risk level:
- MEDIUM
- Trust score:
- 75/100
Open-source (MIT) summarization tool by Peter Steinberger that extracts and summarizes content from web pages, PDFs, images, audio/video, YouTube, podcasts, and RSS. It ships as a Chrome Side Panel extension (with chat and history), a Firefox Sidebar, a CLI, and an optional local daemon for streaming Markdown output. It performs transcript-first media processing, video slide extraction with OCR, and timestamped cards. Users bring their own LLM provider API key: configuration is via environment variables (OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY / GOOGLE_GENERATIVE_AI_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, plus OpenAI-compatible endpoints like Z.AI, NVIDIA, MiniMax) or a local config file at ~/.summarize/config.json. Ollama and other OpenAI-compatible local endpoints are supported for fully local use; if no key is set it can fall back to on-device Gemini Nano. Note: Groq/AssemblyAI/ElevenLabs/FAL keys are used only for audio transcription, not for the summarization LLM. Verified against the live GitHub API on 2026-06-20: 6,226 stars, MIT license, not archived, not a fork, latest release v0.20.0 published 2026-06-19, last pushed 2026-06-19.
Why this trust score (75/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 13/25: The key is persisted in browser local storage, which any script on the page can read.
- Request Routing 17/20: Requests go straight from you to the AI provider.
- Transparency 20/20: Source is public under MIT, so anyone can check how the key is handled.
- 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 1/10: Compiled from public documentation by an AI-assisted pass, not independently confirmed.
What was checked
Verification tier RESEARCH_ASSISTED, 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] Supports a local model backend, so it can run with no cloud provider key at all. source
- [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-08-13, about 0 month(s) ago. source
How your API key is handled
Your API key is stored in your browser's local storage. 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
Open the extension/app settings, paste your provider API key (kept in your browser), and pick a model.