Store your LLM provider keys in Grepture. The proxy automatically fails over between keys and across providers on auth errors, rate limits, timeouts, and server errors — with cross-provider request translation built in.
Grepture manages your LLM provider API keys and uses them to route requests. Configure multiple keys per provider and cross-provider fallback paths. The proxy detects authentication errors, rate limits, timeouts, and server errors — and automatically retries with the next key or provider. Cross-provider fallback translates the request and response format automatically, so your application code never changes.
Add provider keys in the Grepture dashboard. Set a primary key per provider and link fallback keys — same-provider or cross-provider. The proxy handles key selection, error detection (401, 408, 429, 5xx), and format translation between providers. Every fallback attempt is traced in the dashboard. Combine with zero-data mode for full protection without storing request content.
| Provider | Name | Key | Default model | Status |
|---|---|---|---|---|
| OpenAI | prod-openai-1 | ...a3f2 | gpt-4o | primary |
| OpenAI | prod-openai-2 | ...7d9e | gpt-4o | fallback |
| Anthropic | prod-anthropic | ...k4m1 | claude-sonnet-4-20250514 | primary |
npm install @grepture/sdk — wrap your client — done.
Free for up to 1,000 requests/month · No credit card required
Get Started Free