Docs
Virtual Keys
Virtual Keys
Manage API access with virtual keys for rate limiting, cost tracking, and access control.
Virtual keys in Elyxir manage API access to LLM providers. They enable rate limiting, cost tracking, and fine-grained access control for your organization.
Overview
Virtual keys provide:
- Rate Limiting: Control requests per minute per key
- Cost Tracking: Monitor spending per key
- Access Control: Scope keys to specific models or uses
- Quota Management: Set spending limits per key
Accessing Virtual Keys
- Sign in to studio.elyxir.ai
- Go to Virtual Keys in the main navigation
- View, create, and manage your keys
Key Components
Developer API Keys
External-facing keys for your applications:
- Format:
elyxir_xxxxxxxxxxxxxxxx - Used in the Authorization header
- Generated in Settings > API Keys
Virtual Keys (Internal)
Internal keys that map to LLM providers:
- Automatically created with developer keys
- Linked to your organization's provider credentials
- Managed through the Virtual Keys dashboard
Dashboard Overview
The Virtual Keys dashboard shows:
| Column | Description |
|---|---|
| Name | Key identifier |
| Status | Active or inactive |
| Requests | Total API calls |
| Tokens | Total tokens used |
| Cost | Total spending |
| Rate Limit | Requests per minute |
| Created | Creation date |
Key States
| State | Description |
|---|---|
| Active | Key is working normally |
| Inactive | Key is disabled |
| Over Limit | Rate or budget limit exceeded |
| Expired | Key has passed expiration date |
Use Cases
Development vs Production
Create separate keys for:
- Development: Lower limits, test environment
- Staging: Medium limits, pre-production
- Production: Higher limits, live traffic
Per-Application Keys
Create keys for each application:
- Web App: Frontend chat interface
- API Service: Backend processing
- Mobile App: Mobile client requests
Per-Team Keys
Assign keys to teams for:
- Independent cost tracking
- Team-specific rate limits
- Clear usage attribution
Best Practices
- Use descriptive names: Identify keys by purpose
- Set appropriate limits: Match limits to expected usage
- Monitor regularly: Review usage patterns
- Rotate periodically: Replace keys every 90 days
- Delete unused keys: Remove keys no longer needed
Related
- Creating Keys - Create new keys
- Rate Limits - Configure limits
- Analytics - Usage tracking