Bring your own key, often shortened to BYOK, means connecting an application to an AI provider account that you control. Instead of buying all processing through the application developer, you provide an API credential and pay the selected provider directly for what you use.
For meeting transcription, this can make the relationship among the recorder, provider, and customer much clearer.
What an API key does
An API key identifies your account when software sends a request to a provider. It is sensitive because it can authorize usage that may be billed to you.
Create the key in the provider’s official account dashboard. Do not paste it into messages, public documents, screenshots, or support requests. If you believe a key has been exposed, revoke it through the provider and create another.
In Quendian, BYOK credentials are stored locally on your Mac. They are not sent to or stored on Quendian’s servers.
The BYOK data path in Quendian
When you choose BYOK transcription, Quendian sends the recorded audio directly from your Mac to the provider configured in Preferences. The request is not routed through Quendian infrastructure.
Transcription and summarization are separate choices. You can configure a supported provider for transcription and another supported provider or compatible local service for summarization.
This distinction matters because the transcript is the input to the summary. Review the data-handling and retention terms of every provider you choose, not only the transcription provider.
How to configure a key
The general workflow is:
- Create an account with a supported provider.
- Add billing or usage limits in that provider’s dashboard if required.
- Generate an API key.
- Open Quendian Preferences.
- Select the provider for transcription.
- Paste the key into the provider’s credential field.
- Select and configure a summarization option.
- Make a short test recording before using the setup for an important meeting.
The test recording should include both your microphone and audio playing through the Mac. Confirm that the transcript appears, the summary completes, and the expected provider shows usage in its dashboard.
Why someone might choose BYOK
BYOK is useful when you want:
- a direct billing relationship with the provider;
- control over which supported provider processes the request;
- visibility into provider-level usage;
- the option to change providers without changing the recording workflow;
- no Quendian subscription for the BYOK path; or
- compatible local summarization on your own Mac.
Quendian does not charge for BYOK processing. Provider usage may still cost money, depending on the provider and account.
When Quendian Cloud may be simpler
BYOK also creates responsibilities. You manage credentials, provider billing, account limits, and compatibility. A revoked key or exhausted provider balance can interrupt processing.
Quendian Cloud is the alternative for people who do not want to manage those pieces. You sign in, select the hosted path, and use the included transcription and summarization allowance.
Neither approach is universally better. BYOK prioritizes direct control. Quendian Cloud prioritizes convenience.
Keep the setup maintainable
Use separate keys when a provider supports them, set reasonable spending limits, and revoke credentials that are no longer needed. Keep a short test recording available so you can verify a configuration after changing providers or settings.
The main benefit of BYOK is choice without changing the rest of the meeting workflow. Quendian still captures the call on the Mac, creates a session, lets you review the result, searches completed notes locally, and exports them as Markdown.