OpenAI-compatible LLM gateway for any client-side application (browser, mobile, React Native, Flutter, VS Code extensions, browser extensions, Electron, smart TV, and more). Routes requests to OpenAI, Anthropic, Gemini, Groq, Mistral, and 200+ models, handling CORS, key encryption, and streaming without a dedicated backend. Uniquely supports BYOK (bring your own key): users connect their own provider API keys so the developer pays nothing for inference. Use for multi-provider LLM access, client-safe AI API calls, or any product where users supply their own API credentials. Use when this capability is needed.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
OpenAI-compatible LLM gateway for any client-side application (browser, mobile, React Native, Flutter, VS Code extensions, browser extensions, Electron, smart TV, and more). Routes requests to OpenAI, Anthropic, Gemini, Groq, Mistral, and 200+ models, handling CORS, key encryption, and streaming without a dedicated backend. Uniquely supports BYOK (bring your own key): users connect their own provider API keys so the developer pays nothing for inference. Use for multi-provider LLM access, client-safe AI API calls, or any product where users supply their own API credentials. Use when this capability is needed.
byok-relay Skill
What this skill does
This skill helps you integrate byok-relay - an OpenAI-compatible LLM gateway for any client-side application (browser, mobile, extensions, Electron, smart TV, and more) that handles CORS, encrypts API keys, and supports multiple providers through a single relay endpoint.
Use this skill whenever:
A user wants to call OpenAI, Anthropic, Gemini, Groq, Mistral, or other LLMs from a client-side app (browser, mobile app, VS Code extension, browser extension, Electron app, smart TV app, etc.)
A user asks about CORS errors when calling AI APIs from frontend code
A user needs a self-hosted or lightweight LLM proxy/gateway
A user wants multi-provider LLM access without managing separate SDKs
A user asks "how do I let users use their own OpenAI/Anthropic keys?"
A user asks "how does my company use one shared API key for the whole team?"
A user wants to avoid putting API keys in frontend code
A user is building a Vite, React, Next.js, Vue, or plain HTML app that needs AI
A user is building on Lovable, Bolt, Framer, Replit, or Vercel and needs AI capabilities
A user wants zero inference costs by having users (or their organization) supply their own API credentials
A user is building a B2B or team product where a company admin manages one shared API key
The problem it solves
Browser apps can't call AI APIs directly:
api.openai.com, api.anthropic.com, etc. block cross-origin requests from browsers, mobile webviews, and extensions via CORS
Putting API keys in client-side code (browser, mobile app, extension) exposes them to every user
Building a backend just to proxy requests adds maintenance overhead
Managing separate SDKs for each LLM provider adds complexity
byok-relay is a single relay that handles all of this: OpenAI-compatible endpoint, CORS-safe, multi-provider, with optional BYOK so users (or their organization) supply their own credentials and the developer pays nothing for inference.
Two BYOK patterns - both supported
Individuals / prosumers: Each user registers their own personal API key. Common for developer tools, research UIs, AI power-user products.
Teams / B2B (company-managed key): A company admin registers one shared company API key via POST /keys/:provider (e.g. /keys/openai). In the current implementation, keys are stored per relay-token (user); to share a key across team members, the admin can share their relay token or register the same company key under each member's account. Org-level key sharing (one stored key → multiple relay tokens) is on the roadmap. The developer doesn't touch the key — it belongs to the customer's organization.
Setup - choose your path
Option A: Use the managed relay (recommended for frontend-only apps)
If you are building a frontend-only, browser-only, or client-side-only application (Lovable, Bolt, Replit, plain HTML, Vite, React without a backend, mobile app, extension), use the hosted relay directly. No cloning, no server setup needed.
constRELAY_URL = 'https://relay.byokrelay.com';
That's the only configuration needed. Skip to the Integration section below.
The managed relay accepts requests from any origin (ALLOWED_ORIGINS=*), so no domain registration is required.
Option B: Self-host the relay (if you have a backend or want full control)
Use this if you want to run your own relay on your infrastructure (VPS, Railway, Fly.io, etc.).
Deploy: Works on any VPS, Railway, Fly.io, or self-managed server
When NOT to use byok-relay
You need advanced model routing, automatic fallbacks, or per-request spend analytics → consider adding those on top of byok-relay or using a dedicated routing layer
You are building a pure server-side application with no client-side component and no need for BYOK → use provider SDKs directly
