Bring Your Own Key [BETA]
Bring your own provider API keys
This feature is currently in beta. For any issues or feedback, please contact us via Discord or support@cortecs.ai.
BYOK lets you connect your own provider credentials to Cortecs, allowing requests to be routed through your own provider account.
When BYOK is enabled for a provider, Cortecs can use your API key either before or after the Cortecs-managed endpoints, depending on the selected usage mode. This gives you more control over provider billing and quota while still using Cortecs routing, model selection, and API interface.
Adding a Provider Key
To add your own provider key:
Go to Settings
Select the BYOK tab
Click Add provider key
Select the provider
Enter the required credential fields
Choose a usage mode
Click Save
Only project administrators can add, update, or delete provider keys.
BYOK Usage Modes
Cortecs supports two BYOK modes:
Prefer my key
Cortecs tries your provider key first. If the request fails, Cortecs retries using the Cortecs-managed endpoints.
Yes, as backup
Required
Fallback to my key
Cortecs first tries its managed endpoints. If those endpoints fail, Cortecs retries the request using your provider key.
Yes, first
Required
Billing
There is currently no Cortecs usage fee for requests served using your own BYOK key. BYOK is currently available at no additional cost on the Cortecs platform.
Supported Providers
Providers Requiring Only an API Key
For the following providers, you only need to provide the provider API key:
Mistral
OVH
Nebius
Tensorix
Inceptron
Infercom
Ionos
Scaleway
AKI
Berget
Amazon Bedrock
Cortecs currently supports Bedrock API keys for BYOK. AWS key authentication is not supported yet for BYOK, but may be added in the future.
Google Vertex AI
For Google Vertex AI, you need to provide a Google service account JSON file. You can download this file from the Google Cloud Console.
Ensure the service account has permission to access Vertex AI and the models you intend to use.
You do not need to specify a region. Cortecs automatically routes through supported EU regions. Ensure the models you plan to use are enabled in the appropriate EU regions of your Google Cloud project.
Azure OpenAI
Cortecs currently supports Azure OpenAI resources for BYOK using:
You need to provide:
Resource name
API key
API version, optional
Cortecs automatically constructs the Azure endpoint from the resource name.
Example:
Azure OpenAI requires explicit model deployments. The deployment name in your Azure resource must match the Cortecs model ID you are requesting.
More advanced BYOK configuration options will be added over time based on user needs.
Last updated