One API Key. Zero Lock-In.
FreeRouter is a meta router for LLM inference — think ad mediation for AI. Point your app at one OpenAI-compatible endpoint, bring your own provider keys, and route every request across OpenRouter, Vercel AI Gateway, Cloudflare AI Gateway, and more with rules you control.
What is FreeRouter?
FreeRouter sits between your application and the LLM gateways you already use. You integrate against a single, OpenAI-compatible API. Behind the scenes, FreeRouter picks a target gateway per request according to your routing rules, swaps in the right provider key, normalizes the request and response format, and forwards it. Your code never changes when you re-balance traffic or add a new provider.
The name is about freedom, not price — free from vendor lock-in. If a gateway raises prices, drops a model, or degrades, you flip a routing rule instead of rewriting your integration.
Core Concepts
- Provider key (BYOK) — a key you already hold for a gateway like OpenRouter or Vercel AI Gateway. You add it to FreeRouter; it is encrypted at rest and used only to forward your requests.
- FreeRouter API key — the single key your application sends. It carries your routing configuration and API shape.
- API shape — the request/response format a key speaks. Default is OpenAI; per key you can switch to OpenRouter, Anthropic, or Google shapes.
- Routing rule — how requests are distributed across gateways: a %-split, or a priority order with failover.
- Workspace — a personal or team container for keys, providers, and rules.
The Drop-In Promise
Adoption shouldn't cost you a rewrite. FreeRouter is a drop-in replacement for the OpenAI API and its common cousins:
- Change your base URL to
https://api.freerouter.com/v1. - Swap your API key for your FreeRouter key.
- Keep calling
/v1/chat/completionsexactly as you do today.
See the Quickstart for copy-paste curl, Python, and Node examples.
How a Request Flows
https://api.freerouter.com/v1/chat/completions with your FreeRouter key in the Authorization header.