Bring Your Own Keys (BYOK)

Connect your own OpenAI, Anthropic, Gemini, and Deepgram API keys to control AI model routing and infrastructure costs.

What it does

Verabase runs on a Bring Your Own Key (BYOK) architecture. Rather than charging markups or pricing per conversation query, Verabase securely stores your LLM and Audio API keys and forwards context requests directly to your accounts. You retain complete ownership over your models, data policies, and actual developer platform fees.

Data Flow & Key Security

Key processing is built with secure, encrypted routing standards:

Data Read: API Key tokens entered inside settings. Keys are securely encrypted at rest inside our databases using Key Management Services (KMS).
Data Written: Verabase injects the keys into the Authorization request headers when making inference calls to OpenAI, Anthropic, Gemini, or Deepgram.
Sync Frequency: Real-time key checks verify that authorization parameters are valid during setup. Keys are fetched during query pipelines.

Scope & Supported Providers

Each provider link points to the official developer key management configurations:

OpenAI: Supports models (GPT-4o, GPT-4-turbo, GPT-3.5) and embedding parameters. Refer to the OpenAI Authentication Reference.
Anthropic: Injects context parameters to Claude model engines. Refer to the Anthropic Authentication Reference.
Google Gemini: Utilizes Gemini Pro vision and text pipelines. Refer to the Google Gemini API Authentication Reference.
Deepgram: Stream WebRTC audio call transcriptions and conversions.

Setup guide

Estimated setup time: ~6 minutes. Authentication type: Developer API Key keys (KMS encrypted). Administrator access inside LLM provider consoles required to generate keys.

Access API Keys settings

In your Verabase dashboard, navigate to Settings → API Keys. This page displays inputs for each supported provider.

Generate API Keys in Provider consoles

Access your OpenAI Developer, Anthropic Console, Google AI Studio, or Deepgram Console. Create a new API Key with standard request scopes. Set budget controls to prevent spend alerts.

Paste keys into Verabase Settings

Paste your API keys into the corresponding fields inside the Verabase dashboard, then click Save Keys. Verabase encrypts the credentials using KMS keys instantly.

Validate key connectivity

Click Test Keys to fire a lightweight validation request. A green checkmark confirms authentication is valid. The keys are ready to handle agent queries.

Where it shows up

Model Selection settings: Once active, matching model profiles display inside AI Agents → Advanced Settings → Model dropdown selection menu. You can route complex tasks to advanced models and simpler questions to faster ones.

Troubleshooting & Common Issues

API Key rejected (HTTP 401): Check if the key was pasted with typos or leading/trailing spaces. Confirm that the key has not been deleted or suspended inside the provider's developer console.
Rate limits exceeded (HTTP 429): If query loads hit rate limits, check your billing tier inside the provider portal. Most new developer accounts are restricted to low rate tiers until they complete an initial deposit.

Frequently asked questions

Which LLM providers are supported?

Verabase supports OpenAI, Anthropic, Google Gemini, and custom OpenAI-compatible endpoints (e.g. Together AI, Anyscale).

Does Verabase charge any markup on model tokens?

No, you pay your LLM providers directly. Verabase does not mark up API usage costs.

Are my API keys stored securely?

Yes, all API keys are encrypted at rest using AES-256 with keys managed in secure hardware security modules (HSM).

Related integrations

Ready to save on API costs?

Join the waitlist for early access to the self-healing knowledge platform.

Get early access to BYOK settings