Your AI keys. Your cost control.
Already subscribed to OpenAI, Anthropic, or Google AI? Connect your existing API keys to BuilderVerse and use the platform as a pure interface layer — pay only for what you use, at your own provider rates.
Pay your rates
Use your existing provider pricing and volume discounts
Encrypted storage
Keys stored with AES-256 encryption, never logged
Direct API calls
Requests go directly to providers — no proxy overhead
API Key Management
Connect your own API keys for any supported provider. Keys are encrypted at rest.
OpenAI
GPT-4o, o1, o3-mini, GPT-4o Mini
Anthropic
Claude 3.5 Sonnet, Haiku, Claude 3 Opus
Google AI
Gemini 2.0 Flash, Gemini 1.5 Pro
Mistral AI
Mistral Large, Codestral, Mistral 7B
Meta (via Groq)
Llama 3.3 70B, Llama 3.2 Vision via Groq
DeepSeek
DeepSeek R1, DeepSeek V3
Cohere
Command R+, Command R, Embed
xAI
Grok 2, Grok 2 Mini
Your keys are safe with us
We take API key security seriously. Here's exactly how we protect your credentials.
AES-256 Encryption at Rest
All API keys are encrypted using AES-256-GCM before storage. The encryption key itself is stored in a separate, access-controlled secrets vault.
Zero Key Logging
Your API keys are never written to application logs, error reports, or analytics pipelines. We have no visibility into your key values after initial encryption.
Direct Provider Calls
API requests using your keys are made directly to the provider — not proxied through any third-party service. Latency is identical to calling the provider yourself.
Scope Recommendations
We recommend creating scoped API keys with only the permissions BuilderVerse needs. Our setup guide shows exactly which permissions to grant per provider.
Easy Key Rotation
Replace any key at any time without downtime. Old keys are immediately invalidated from our system upon replacement — no grace period, no exposure window.
Usage Audit Logs
Scale plan users get full audit logs of which keys were used, when, and for which builder. Detect anomalies or unexpected usage patterns instantly.
Setup guide
Get your first BYOK connection working in under 5 minutes.
Go to your provider's API key page
Each provider has a dashboard where you can create API keys. Use the links in the provider cards above to go directly to the right page.
Create a new key specifically for BuilderVerse — don't reuse keys from other services.
Create a scoped key with minimal permissions
For most providers, you only need "API access" or "Completions" permission. Avoid using admin or billing keys.
For OpenAI: use a Project API key, not your organization key. For Anthropic: a standard API key with default permissions is sufficient.
Copy the key and paste it into the provider card above
Keys are only visible once when created. Paste immediately into the provider card — BuilderVerse encrypts and stores it securely.
If you miss the copy window, simply delete the key at your provider and create a new one.
Verify the connection
After saving, BuilderVerse runs a lightweight verification call to confirm the key is valid. You'll see "Connected" status within a few seconds.
If verification fails, double-check the key has not expired and the correct permissions are set.
Select your key in the builder model picker
When starting a new build or switching models, you'll see BYOK models marked with a key icon. Select them to use your own key for that session.
You can mix BYOK and platform-managed models across different builders in the same project.
Need more help?
Full documentation with provider-specific screenshots
BYOK vs. Platform-Managed Keys
Choose the approach that fits your usage pattern and cost preferences.
Our recommendation: If you already have OpenAI or Anthropic credits, use BYOK for those providers and let BuilderVerse manage models you don't have keys for. You get the best of both — your existing pricing where it applies, zero setup where it doesn't.