Add your API key

1. 1Open the provider's console: console.groq.com/keys for Groq, platform.openai.com/api-keys for OpenAI, and so on.
2. 2Create a new API key. Copy it once (most consoles don't show it again).
3. 3Open Dimmy → Settings → Providers & keys.
4. 4Click the card for your provider to expand it.
5. 5Paste the key in the key field and click Connect.
6. 6The card header shows a connected status pill when the key is accepted.

Where the key lives

• Encrypted at rest in ~/.config/dimmy/keys.enc (or %APPDATA%\dimmy\keys.enc on Windows).
• AES-256-CTR with an HMAC-SHA256 authentication tag, encrypt-then-MAC, so a tampered file is rejected instead of silently decrypted.
• The encryption key is derived on the spot from your username and your machine name. Nothing is written to an OS keyring, so there is no permission popup and no admin password on any platform.
• Decrypted only in memory when Dimmy needs to call the provider.
• Sent only to that provider's endpoint, over HTTPS. A URL with credentials in it, with line breaks, or on plain HTTP is refused, the one exception being a server on localhost.

Multiple keys

Each provider has its own card with its own key field. You can keep keys for Groq, OpenAI, Anthropic, and others simultaneously. Each card shows what the provider can do: speech to text, rewrite, recap.

One provider, up to three keys

Keys are stored per provider and per job, not one per provider. That means the same vendor can carry more than one account.

Most people never need the third one. It exists for the case where the recap should be billed to a different account than your day-to-day dictation, for example a work account for meetings and a personal one for everything else.