Bring your own key: how BYOK works in Reduz
BYOK means Reduz uses an API key from your own AI provider account. You pay the provider directly, pick the model, and no Reduz server sits in between.
BYOK means Reduz uses an API key from your own AI provider account. You pay the provider directly, pick the model, and no Reduz server sits in between.
Pick a summarizer by testing it on your own sources: check that it keeps numbers and attribution, understand the data path and costs, and make sure you can get your notes out.
Summarize a captioned YouTube video next to the player, jump to the moments that matter with clickable timestamps, and keep the result in your local history.
Reduz keeps your API keys and saved summaries in your browser. This covers what that means in practice, what still leaves your device, and how to keep a copy.
Reduz reads PDF text in your browser and sends only the extracted text to the AI provider you choose. Scanned PDFs need OCR first.
A good summary prompt says what to keep, how long to be, and what to do when the source is silent. This walks through writing one in Reduz, with placeholders and an example.
Some summarizers keep your notes on their servers, others keep them on your device. Two questions tell them apart: where is the text processed, and where are the results stored?