Skip to main content
api key

Bring Your Own API Key for Notes, Kept in Keychain

Vemoir Team
Vemoir Team Mac meeting records by Aurum Avis Labs · Oberägeri, Switzerland
7 min read

Hero photo by zoshuacolah on Unsplash

Bring your own API key when you want OpenAI or Anthropic to write text for you, and you want that choice spelled out. Vemoir stores the credential in the macOS Data Protection Keychain. Saving or verifying a key does not turn it on. You confirm an activation that routes Ask Vemoir, documents, meeting artifacts, and custom artifacts to that one provider. Audio and speaker separation stay on the Mac. If the key is missing, the endpoint changed, the provider is down, or the call fails, the operation stops. Nothing silently picks another backend.

The Mac app itself is a one-time App Store purchase: CHF 20 in Switzerland, €24.99 in Germany, Austria, France, and Italy, $22.99 in the US. The provider bills its API for the text you send. Check current rates on the provider site as of September 2026. Vemoir can keep a content-free receipt with provider, model, timing, outcome, usage, and a dated cost estimate when compatible pricing exists. The receipt does not contain the prompt, the transcript, names, or the key.

What a bring-your-own API key is allowed to see

External generation is text only. Raw audio, files, images, and remote URLs are not part of the request. The transcript text and the notes you already have on the Mac can be what you chose to process as text, because that is how a summary gets written. The recording itself does not leave for speech-to-text. Parakeet or Whisper already did that locally, or they will. Speaker separation does not move to the provider.

When you generate minutes, Ask Vemoir, or a custom artifact, the app sends the text context needed for that job. That can include transcript excerpts, your typed notes, and project glossary terms as plain text. It does not send the audio file. Read the vendor’s API and privacy documentation for retention. Vemoir does not claim compliance on your behalf.

One active source at a time. Activating the key sends Ask, documents, meeting artifacts, and custom artifacts to it. Selecting a local language model, Qwen3 4B or gpt-oss-20b, switches all four back on the Mac. You do not get a blend where Ask uses Anthropic and the minutes use Qwen unless you change the active source between them.

Onboarding can skip the provider entirely. Local models remain the default path.

  • Opt-inOff by default

    Cloud writing models need your key and a toggle.

  • AudioStays local

    Only text prompts leave the Mac when enabled.

  • VendorYour account

    Billing and retention follow that provider.

Want minutes without sending text to a vendor? Leave the key off and let the local model write on the Mac. The same recording flow is in Ask questions about a meeting transcript.

Who pays for API usage

The App Store price covers the Mac app, not provider tokens. Heavy Ask use can show on the provider bill while the key stays active. Content-free receipts in Privacy settings help you reconcile usage without storing meeting text.

Turn it on without surprising yourself

  1. Open Settings, AI. The same flow exists in advanced onboarding, and you can refuse it there.
  2. Choose OpenAI or Anthropic. Put the key in. It goes to the Keychain. The rest of the configuration is not the secret.
  3. Verify if you want to know the key works. Verification is not activation.
  4. Read the activation disclosure and confirm it. That confirmation is the moment selected meeting text can go to the provider.
  5. After a meeting, look for the visible external-processing mark on output that used the key. A local summary will not wear that mark.

Removing the key stops new requests and cancels registered work for that provider. It does not delete text you already generated. Receipts can be exported or deleted in Privacy and Data settings. They are content-free on purpose.

There is no per-request sheet that pauses the recording so you can read the payload. The activation is the decision, up front. If that is too broad for a given client, do not activate the key for that work. Use the local model.

Where a local model is the better choice

A bring-your-own key is the better choice when you already pay a provider, you want that model for writing, and you accept that meeting text leaves the Mac under a choice you confirmed. The local model is the better choice when:

  • The audio or the transcript must not go to a third party at all. Leave the key off. Local Qwen or gpt-oss writes on the Mac. Apple Intelligence, where the Mac has it, can clean up artifacts without a provider key.
  • You do not want an API bill that moves with usage. The app purchase does not cap the provider. Their invoice does.
  • The provider fails mid-summary. You want the job to stop, not to slip onto a different company. That is what happens. Resume when the key works, or switch the active source to the local model yourself.
  • You only needed speech-to-text. The key does not transcribe. Downloading Parakeet or Whisper is the speech step.

A shared team key vault, SSO for the whole company, and a private model host are not this feature. This is your key, in your Keychain, on this Mac.

The free browser tools are not a key slot either. /tools/transcribe-recording runs a public Whisper model in the tab on a file you already have, up to 15 minutes, three successful runs a week. It does not take your OpenAI key and it does not label speakers.

Requirements for the app: Apple silicon, macOS Sonoma 14.2 or later, 8 GB of memory, 10 GB free, 16 GB recommended for long meetings.

The setup lives with the other model choices in capture.

A client who forbids cloud text

You recorded locally and the agreement forbids sending meeting content to a model vendor. Do not activate the key to read the disclosure only. Leave it off and let the local model or Apple Intelligence write the draft. On another engagement that allows your company key, activate, export, then remove the key before the next restricted client.

Frequently asked questions

Does bring your own API key send the recording?

No. Requests are text only. Transcription and speaker separation stay on the Mac.

Which providers can I connect?

OpenAI or Anthropic. You activate one text source at a time.

Does saving the key turn it on?

No. You verify if you want, then you confirm activation separately. Until then, writing stays on the local path.

What if the provider errors?

The operation stops. There is no silent fallback to another provider or to a local model you did not select.

Where is the secret stored?

In the macOS Data Protection Keychain. Removing the key blocks new requests. Generated text you already have stays until you delete it yourself.

Will I see that a note used the cloud?

Yes. External output keeps a visible external-processing mark and provider provenance. Receipts in Privacy settings hold no content and can be deleted.

Does this change the App Store price?

No. API usage is billed by the provider, not as a Vemoir seat.

Can I keep audio local and only ask one hard question in the cloud?

Yes, if you activate, ask, then switch the active source back to the local model when finished.

Activate the key only for text you are willing to send, and leave it off when the local model is enough. The switch is in capture.

api key privacy notes
Vemoir Team

Written by

Vemoir Team

Mac meeting records by Aurum Avis Labs · Oberägeri, Switzerland

We build Vemoir, a Mac app for local-first meeting records: capture from the menu bar, transcribe on your Mac, and turn calls into minutes and action items.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, and the free in-browser tools limit (timestamps of successful runs in the current week, no content).

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.