llmrelay
// vs openrouter

OpenRouter alternative

The unified marketplace routing across 200+ models and providers.

We are a smaller, narrower service than OpenRouter: fewer models, no free tier, no cross-provider routing. What we do is sell the premium tiers at half their list price. If that is the trade you want, the numbers are below — along with the cases where you should stay put.

The short answer

Use OpenRouter when

You need obscure models (Kimi, DeepSeek variants, older Llamas) or cross-provider fallback, and list price is acceptable.

Use llmrelay when

You mostly use Claude, GPT, or Gemini and want half of list instead of list.

Head-to-head

OpenRouter
llmrelay
Pricing on premium models
Pass-through list price with no inference markup — $5.00/M input, $25.00/M output on Opus 4.7 — plus a 5.5% credit-purchase fee (Stripe, $0.80 min). BYOK usage carries a 5% fee after the monthly free allowance.
$2.50/M input on Opus 4.7 (50% off)
Billing model
Varies (see homepage)
Prepaid credit, no expiry
Model coverage
See homepage
Claude, GPT, Gemini, Fable
Transparency
Public patch log, hidden-prompt neutralizer
The cost difference, worked out

$375.00 against $187.50

A month of moderate agent traffic: 50M input tokens and 5M output tokens on a flagship Claude model.

OpenRouter
$375.00
llmrelay
$187.50
Difference
$187.50 saved, before their credit-purchase fee

OpenRouter passes through provider list price, which is $5.00/M input and $25.00/M output — 50 × $5 + 5 × $25 = $375. We charge half list, so the same traffic is $187.50. On top of that, topping up $375 of OpenRouter credit by card costs about $20.63 in their 5.5% purchase fee, so the real gap is closer to $208. Their fee schedule is published in their own FAQ; we are not estimating it.

Where OpenRouter wins

Where OpenRouter loses ground

What you give up by switching

Stated plainly, because you will find this out in week two anyway and it is cheaper for both of us if you find out now.

Moving over, step by step

  1. 01 Change the base URL

    Point your client at https://api.llmrelay.dev/v1 instead of https://openrouter.ai/api/v1. Both are OpenAI-compatible, so the request and response shapes are unchanged.

  2. 02 Swap the key

    Replace your OPENROUTER_API_KEY value with an llmrelay key. Most SDKs read a single environment variable, so this is one line in your config.

  3. 03 Drop the vendor prefix from model ids

    OpenRouter namespaces models as anthropic/claude-opus-4.5. We use the plain upstream id, so that becomes claude-opus-5 for the current flagship. This is the only change that touches code rather than config.

  4. 04 Delete the HTTP-Referer and X-Title headers

    Those are OpenRouter-specific attribution headers for their model rankings. We ignore them, so they are harmless if left in place, but they no longer do anything.

Questions people actually ask

Is llmrelay cheaper than OpenRouter?

On the premium Claude, GPT and Gemini tiers, yes, and by a wide margin. OpenRouter passes through provider list price without an inference markup, so a flagship Claude model costs $5.00 per million input tokens there. We charge 50% of list, so the same model is $2.50. OpenRouter also adds a 5.5% fee when you buy credit by card, which we do not. Where OpenRouter can be cheaper is the free tier it offers on many open-weight models — we have no free tier.

Does OpenRouter mark up inference?

No, and it is worth being precise about this because it is a common misreading. OpenRouter genuinely passes through the underlying provider price on inference. Their revenue on paid models comes from the credit-purchase fee: 5.5% with a $0.80 minimum on card payments, 5% on crypto, and 5% on bring-your-own-key usage above their monthly request allowance. So the comparison is not markup against no-markup, it is list price against half list.

What does OpenRouter do that llmrelay does not?

Breadth and routing. They front 200+ models including many we do not carry, and they will automatically fail over between providers hosting the same model. If you need an obscure open-weight model, or you want that cross-provider failover as a product feature, they are the better tool and we would tell you so.

Can I use both at once?

Yes, and for some teams that is the right answer. Both speak OpenAI-compatible, so you can route premium Claude and GPT traffic through us for the price, and keep OpenRouter for long-tail models. The only thing to watch is that model ids differ — they namespace with a vendor prefix, we do not.

Figures for OpenRouter come from OpenRouter's own documentation, checked 31 July 2026. If they have changed their pricing since and we have not caught it, the error is ours — check their page before you decide.

Migrating from OpenRouter?

Both providers speak OpenAI-compatible / Anthropic-compatible. Swap two env vars and your existing app keeps working.

Get API key →