LiteLLM vs OpenRouter
LiteLLM scores higher on the AgentReady, 84/100 against 81/100. They differ on 21 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
LiteLLM. The AI Gateway for platform teams.
OpenRouter. OpenRouter is a unified interface for AI models that provides access to hundreds of AI models through a single API endpoint.
Where LiteLLM is ahead
LiteLLM passes search discoverable, public docs discoverable and mcp discoverable, and OpenRouter does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: openapi / spec quality, response examples provided, errors and status codes documented and limits / constraints documented. OpenRouter misses those.
And on adopt, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available and mcp integration available. OpenRouter misses those.
Finally, on operate, canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented and observable execution. OpenRouter misses those.
Where OpenRouter is ahead
OpenRouter passes clear canonical domain and clear product positioning, and LiteLLM does not. That is discover, whether an agent can find the product at all without being told it exists.
What neither does
Both fail request examples provided, no mandatory sales call, idempotency support, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.
Score, pillar by pillar
The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.
Discover. OpenRouter leads 100 to 80. LiteLLM misses clear canonical domain, clear product positioning; OpenRouter misses search discoverable, public docs discoverable, mcp discoverable.
Understand. Both sit at 92/100 here. LiteLLM misses request examples provided; OpenRouter misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. OpenRouter leads 88 to 80. LiteLLM misses no mandatory sales call, agent-compatible signup flow; OpenRouter misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available, mcp integration available.
Operate is whether an agent can run against it in production and recover when a call fails. LiteLLM leads 82 to 44. LiteLLM misses idempotency support, rate-limit behavior predictable; OpenRouter misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution.
Pricing
LiteLLM starts at $0 and has a free tier. OpenRouter does not publish one and has a free tier.
| LiteLLM plans | OpenRouter plans |
|---|---|
| Open Source $0 | - |
| Enterprise Talk to sales | - |
Signal by signal
| Signal | LiteLLM | OpenRouter |
|---|---|---|
| AgentReady | 84 | 81 |
| Discovery | 80 | 100 |
| Understanding | 92 | 92 |
| Adoption | 80 | 88 |
| Operability | 82 | 44 |
| Public API | Yes | Yes |
| MCP server | Yes | Unknown |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | No |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
LiteLLM clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: LiteLLM and OpenRouter. Alternatives to each: LiteLLM, OpenRouter.
An agent can fetch this as data: POST /v1/compare {"slugs": ["litellm", "openrouter"]}