OmniRoute

Why it's ranked here

MIT licensed, installable from npm, Docker Hub or a desktop build, and unusually explicit about how it fails. The failover policy sorts errors before retrying: timeouts, network errors, rate limits and upstream server errors may move to another service, while authentication, permission and invalid-request errors are not retried blindly, with a default cap of three attempts. A route preview scores every candidate and names the winner without sending a single upstream request. The security policy documents encrypted credential storage, scoped access for its MCP (Model Context Protocol) tools, and a 48-hour acknowledgment target for vulnerability reports.

What's good

Routing decisions are explainable: each pick returns the ranked list of candidates with their factors and reasons, and services with an exhausted quota or an open circuit breaker are simply ineligible. The free-tier token headline counts each shared pool once and keeps quotas behind regional identity checks out of the total. Stored API keys and tokens can be encrypted with AES-256-GCM. The server refuses to start without its signing secrets and rejects known-weak values like changeme. Every MCP tool call is written to an audit log, and a call missing the required scope is refused and logged.

Tradeoffs

Credential encryption is off by default: without a storage encryption key, secrets are kept in plain text. The prompt-injection guard is described by the project itself as best-effort, only high-severity matches are blocked, and the guardrail framework fails open, so an error never stops traffic. The network layer spoofs browser-like TLS fingerprints and mimics native client headers to reduce bot detection, which sits uneasily with some providers' terms; the README marks 13 providers as avoid in its terms-risk catalogue. Free-tier totals are re-audited every two weeks and move in both directions. The surface is very large, from MITM proxying to memory and skills.

How to use it well

Fits a developer who runs several coding agents across a mix of paid subscriptions and free tiers and wants one address with automatic fallback. Set the two required signing secrets and a storage encryption key before first start, and run the container read-only with a data volume as the security policy shows. Use the route preview to confirm which service a request would hit before spending quota. If agents reach it over MCP, turn on scope enforcement. It does not provide provider uptime guarantees, and the hosted cloud sync service is outside the open-source scope.

Observed

License

MIT

Language

TypeScript on Node.js, built on Next.js

Runtime requirement

Node.js 22.22.2 or newer within 22, or Node.js 24 through 26

Packaging

npm package with an omniroute command-line binary, Docker image, Electron desktop build

Interfaces

OpenAI-compatible HTTP API, MCP server over stdio, SSE and Streamable HTTP, A2A server over JSON-RPC 2.0

Local storage

SQLite, with optional AES-256-GCM encryption of stored credentials

Required configuration

JWT and API key signing secrets; server fails fast without them

Vulnerability reporting

GitHub Security Advisories, not public issues