Providers & API keys
Voisu has no account and no server of its own. It sends your audio straight to the speech providers you configure, with your own API keys, and you pay them directly for what you use.
Why two providers
- DeepgramStreams your audio while you talk and returns a live transcript.
- GroqTranscribes the whole Recording once you stop. Long Recordings are sent in overlapping pieces.
Each gives Voisu a Source Transcript. Voisu reconciles the two into the one Transcript it delivers, so a dropped stream or a misheard word from one provider doesn't cost you the sentence. Groq's language model also helps with that reconciliation and formatting, so Groq receives the Source Transcript text as well as the audio.
On Windows both keys are required. On Linux, Deepgram streaming can be switched off with voisu deepgram off (and back on with voisu deepgram on).
Get your keys
Groq. Sign in to the Groq console, open API Keys and create a key.
Deepgram. Sign in to the Deepgram console and create an API key for your project.
Check each provider's own site for current pricing and free allowances. Voisu doesn't add any charge of its own.
Adding keys on Windows
On first launch Voisu opens its setup screen. Get a free API key on each card opens that provider's console.
Paste each key into its box. Show reveals what you pasted.
Choose Save and start. Voisu checks every new key with its provider and saves only when they all pass. The Windows setup guide has screenshots of each step.
Keys are stored in Windows Credential Manager under your user account, as groq-api-key.Voisu and deepgram-api-key.Voisu. Voisu never shows a saved key again. To change one, open Settings → API keys and choose Replace.
Adding keys on Linux
voisu setup asks for both keys and checks them. To change one later:
$ voisu auth set groq $ voisu auth set deepgram # check a saved key with its provider: $ voisu auth verify groq
voisu auth set reads the key from standard input, so it never appears in your shell history as an argument.
Keys are stored in your desktop's keyring through the Secret Service (KWallet on KDE Plasma, GNOME Keyring on GNOME). If no Secret Service is available, Voisu falls back to a file only you can read, ~/.config/voisu/credentials, and says so loudly when it writes there.
Keys never leave your machine except in requests to the provider they belong to, and they live in your OS keyring rather than in Voisu's settings files. See Privacy.
Local transcription on Linux
On Linux, voisu setup also offers Local: a model downloaded once, with your consent, that then runs offline with no provider keys. It's English only.
- With an NVIDIA GPU that has at least 3.5 GB of memory:
distil-large-v3.5-int8(about 2.98 GB download, MIT licence). - Any other computer:
parakeet-tdt-0.6b-v3on the CPU (about 770 MB download, CC-BY-4.0 licence).
Nothing downloads until you agree to the size and licence. Local never falls back to the cloud: if the model isn't ready, the Recording fails instead. Switch with voisu mode local or voisu mode cloud, and remove the model with voisu local remove.