Interactive demos showing how to route AI provider traffic through Grepture.
Each example is a standalone Vite + React app. API keys are entered in the browser — nothing is stored or processed server-side.
Please remove dangerouslyAllowBrowser: true from the options before using in production!
| Folder | Provider | SDK |
|---|---|---|
openai/ |
OpenAI | openai + @grepture/sdk |
anthropic/ |
Anthropic | @anthropic-ai/sdk + @grepture/sdk |
gemini/ |
Google Gemini | @google/genai (custom fetch) |
vercel-ai-sdk/ |
Vercel AI SDK | ai + @ai-sdk/openai + @grepture/sdk |
stored-keys/ |
Stored provider keys | openai + @anthropic-ai/sdk + @grepture/sdk |
Shows how to use Grepture's stored provider keys — no OpenAI/Anthropic key in
your client code at all. Configure keys in Settings → API → Provider Keys, then
omit apiKey from grepture.clientOptions(). The proxy resolves the team's
stored key for the detected provider and automatically fails over to any
configured fallback chain on 5xx (including cross-provider fallback with
on-the-fly request/response translation).
cd openai # or anthropic, gemini
npm install
npm run devOpen http://localhost:5173, enter your Grepture and provider API keys, and send a prompt.
Each example sends a prompt containing fake PII (name, email, phone, SSN, address) through the Grepture proxy. If you have redaction rules configured, you'll see the PII stripped from the request before it reaches the AI provider.