Provider Scoping
Restrict API keys to specific providers. A scoped key can only access the provider it's pinned to. Attempting to use a scoped key with a different provider returns 403 Forbidden.
Creating a Scoped Key
When creating a key at /keys, select a provider from the "Provider Scope" dropdown. Leave empty for unrestricted access.
How It Works
| Key Scope | Request Model | Result |
|---|---|---|
| None (unrestricted) | groq/llama-3.3-70b-versatile | 200 OK |
| groq | groq/llama-3.3-70b-versatile | 200 OK |
| groq | openai/gpt-4o-mini | 403 Forbidden |
| openai | openai/gpt-4o | 200 OK |
| openai | claude/claude-3-5-sonnet | 403 Forbidden |
Use Cases
Team Access Control
Give different teams keys scoped to different providers.
Cost Control
Pin keys to cheap providers to prevent expensive accidental usage.
Client-Side Keys
Scope keys embedded in frontend apps to limit exposure.
Environment Separation
Dev keys → free OpenRouter, prod keys → Groq for speed.