BYOK
Use your own provider keys while Spro handles routing, guardrails, caching and tracing.
What is BYOK?
Bring Your Own Key (BYOK) lets you connect your own provider API keys to Spro. Requests served through your keys keep using Spro's gateway, routing, guardrails, caching and observability, while the provider account, pricing and billing stay yours. Spro tries your key first when a workspace has a credential for the requested provider.
Bring Your Own Key (BYOK) lets you connect your own provider API keys to Spro. Requests served through your keys keep using Spro's gateway, routing, guardrails, caching and observability, while the provider account, pricing and billing stay yours.
BYOK is the default path. When a workspace has a credential for the requested provider, Spro tries it first, so traffic lands on the accounts you already pay for.
Key features
What this feature does for your requests.
- Add a provider credential once at the workspace level
- Works for every request to that provider with no per-request headers
- Falls back to Spro's managed provider access when a key cannot serve the request, where available
- Usage is recorded per request: model, provider, tokens, latency and key used
- Credentials are encrypted at rest and shown only as a masked reference after saving
How it works
4 steps, from setup to the first request.
- 01
Add a key once
Store the provider credential at the workspace level from the BYOK page.
- 02
Send requests as usual
Keep calling Spro with the same endpoint and model. Nothing in your app changes.
- 03
Spro uses your key first
When a BYOK credential exists for the requested provider, Spro serves the request with it.
- 04
Fallback if it fails
An authentication error, rate limit or provider error can fall back to managed access where available.
Is it the right fit?
Specific situations where this feature helps, and where it does not.
Good fit if
- You already hold committed spend or credits with a provider
- Security teams keeping provider secrets out of app repos and CI
- You want gateway routing and logs while the provider bills you directly
Not a good fit if
- Your provider contract does not allow third-party routing of your key
- You want one invoice from Spro that covers provider usage
- You have no provider account yet. Start with managed access
Billing options
Who pays for model usage, depending on the key a request uses.
Spro managed
Spro credits
Charged to your Spro balance
- Spro provider access
- Usage billed against your Spro credits
- Full routing and guardrails
Your own key (BYOK)
Provider rates
Billed by your provider
- Not charged against Spro credits
- Usage still recorded per request
- Routing, guardrails, caching and tracing still apply
Supported providers
You can add a key for any of these.
- Anthropic
- Azure
- Cerebras
- DeepSeek
- Google AI Studio
- Groq
- MiniMax
- Mistral AI
- Moonshot AI
- OpenAI
- Perplexity
- SambaNova
- Together
- xAI
- Xiaomi
- Z.AI
BYOK FAQs
Common questions about BYOK.
Route every AI request through SPRO.
One OpenAI-compatible API for 350+ models, with intelligent routing, 29 built-in guardrails, observability, and automatic failover.
