Send one OpenAI-shaped request
Keep the SDK you already use and change the base URL. Chat completions, streaming, tool calls and embeddings all arrive in the same shape.
LLM Gateway puts one OpenAI-compatible endpoint in front of 40+ providers. Route by price or latency, fall back automatically when a provider degrades, and see exactly what every request cost.
Pick a provider and model, set the sampling parameters and see the routed request, the fallback order and the estimated cost before it leaves your browser.
Run the sample prompt to see the routed answer, the provider that served it and the exact cost of the call.
Sandboxed preview: the gateway decisions are simulated in your browser and no provider call is made.
Sign in with Google and open the playground with an active plan. Accounts without a subscription are sent to pricing.
The gateway is a thin, opinionated layer: your request goes in, a policy picks the provider, failures are absorbed, and the result carries its own cost.
Keep the SDK you already use and change the base URL. Chat completions, streaming, tool calls and embeddings all arrive in the same shape.
Name a model directly, or route by price ceiling, latency target and context length, and let the gateway pick the cheapest provider that satisfies it.
When a provider errors, rate limits or times out, the request is retried on the next healthy provider with the same body and streamed back to the caller.
Every call is logged with provider, model, latency, token counts and cost, so spend can be broken down by key, project, team or feature.
Routing is the start. The gateway also carries the keys, the policies, the traces and the cost records that production traffic needs.
One endpoint for every provider, with request normalisation, tool calling, JSON mode and streaming preserved across vendors.
Browse 40+ providers and their models with live context windows, modalities and per-million-token prices before you ship.
Retries, timeouts, hedged requests, circuit breakers and provider fallbacks configured per route instead of per client.
Cost per feature, per customer and per key, plus budget alerts and hard limits that stop a runaway loop before the invoice does.
Issue scoped keys per environment, rotate provider credentials centrally and keep vendor secrets out of your application code.
Traces for every request with provider latency, retry history, token breakdown and the policy that produced the route.
A snapshot of the catalog behind the gateway. Prices are per million tokens and move with the vendor, so routing policies stay honest.
$2.50 / $10.00$0.15 / $0.60$1.10 / $4.40$3.00 / $15.00$1.00 / $5.00$15.00 / $75.00$1.25 / $10.00$0.30 / $2.50$0.27 / $0.85$0.11 / $0.34$0.28 / $0.42$0.55 / $2.19$2.00 / $6.00$0.30 / $0.90$3.00 / $15.00$0.20 / $0.50$0.11 / $0.34$2.50 / $10.00$2.50 / $10.00$3.00 / $15.00$1.00 / $1.00$0.20 / $0.60$0.60 / $2.50Plus custom OpenAI-compatible endpoints, Azure deployments, Bedrock and self-hosted inference behind the same key.
The gateway speaks the OpenAI API, so the migration is measured in lines, not sprints.
curl https://api.llmgateway.lol/v1/chat/completions \
-H "Authorization: Bearer $LLM_GATEWAY_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "smart/cheapest",
"messages": [{ "role": "user", "content": "Summarise this diff" }],
"stream": true
}'Failover is a policy, not an if-statement in every service. The gateway retries, hedges, breaks circuits and probes providers back into rotation.
Ordered fallback chains per route: if the primary provider fails or rate limits, the next healthy provider answers the same request.
Per-route timeouts with jittered retries, plus hedging for latency-sensitive traffic that cannot wait for a full timeout.
Failing providers are removed from rotation automatically and probed back in, so one vendor incident does not become yours.
Recovery happens before the first token is flushed, so clients never receive a half-written answer from a dead provider.
Spend is recorded per request and can be grouped by key, project, customer or feature — with limits that act before the invoice arrives.
Example report for a product running support, summarisation, code review and search traffic through one gateway.
Monthly or annual billing through Stripe. Every plan includes the full provider catalog, routing policies and per-request cost records.
$19/ month
$190 a year, two months free
For a first product behind one gateway.
$49/ month
$490 a year, two months free
For teams shipping to production.
$199/ month
$1,990 a year, two months free
For platform teams with real traffic.
Annual plans are billed once a year and include two months free compared with monthly billing. Cancel at any time from billing settings.
Short answers about the gateway, the providers and how billing works.
An LLM API gateway sits between your application and every model provider. You call one OpenAI-compatible endpoint and the gateway handles provider credentials, request normalisation, routing, retries and failover, then returns one usage and cost record for every call.
More than 40 providers and several hundred models, including OpenAI, Anthropic, Google, Meta Llama, Mistral, DeepSeek, xAI, Groq, Cohere, Perplexity, Together and Fireworks. The catalog follows vendor releases, and any OpenAI-compatible endpoint can be added as a custom provider.
No. The API is OpenAI compatible, so in most stacks the only change is the base URL and the API key. Streaming, tool calls, structured outputs, vision inputs and embeddings keep working, and switching models is a single string change.
Each route has an ordered provider list plus timeout, retry and circuit-breaker settings. If the primary provider errors, rate limits or times out before the first token, the request is retried on the next healthy provider with the same body, and failing providers are probed back into rotation automatically.
Yes. Every request records provider, model, token counts, latency and cost. Spend can be broken down by key, project, team or feature, with budget alerts and hard limits that stop traffic before it exceeds the ceiling you set.
The playground on the home page is a gated preview that shows routing, fallback and cost behaviour in your browser. It needs a Google sign-in and an active plan; accounts without a plan are sent to the pricing page.
Sign in with Google, open the playground and price a request against the whole catalog before you change a line of production code.