LiveKit Agents vs OpenRouter
Side-by-side trajectory, velocity, and editorial themes.
LiveKit Agents added Answering Machine Detection — voice agents are becoming a serious telephony runtime.
LiveKit Agents is releasing roughly twice a week along the 1.5.x line, accumulating telephony-grade primitives around its voice loop. The headline is Answering Machine Detection in 1.5.9 — an LLM-classified detector for what kind of endpoint an outbound call hit. Surrounding work is split between reliability (barge-in cooldown, interruption guards, preemptive-generation tuning, observability retries) and provider breadth (Perplexity Responses, Soniox, Speechmatics, Cerebras, xAI, Rime WebSocket TTS). The mcp_servers parameter was also deprecated on Agent and AgentSession.
The product is converging on a real contact-center runtime, not just a realtime meeting agent. AMD, warm transfer, DTMF handling, recording retries, and avatar join/playback metrics are the feature surface phone deployments demand. The provider plugin universe keeps widening; LiveKit positions itself as the neutral broker between voice models and the actual network. Internal cleanups (mcp_servers deprecation, instruction parts, AvatarSession base class) suggest a tidying pass before a 1.6 cut.
Expect more telephony primitives — supervisor barge-in, richer DTMF flows, call-recording controls — and a unified MCP configuration surface across Agent and Session as the mcp_servers deprecation lands fully.
OpenRouter is becoming a full agent platform, not just a model router.
OpenRouter has rolled out an Agent SDK, universal web search and fetch for any tool-calling model, dedicated audio APIs for TTS and transcription, and a response cache that drops cost to zero on repeat requests. It is also publishing pricing analyses that benchmark frontier-model cost shifts. The April-30 'release spotlight' frames the past month as a multi-product push rather than incremental shipping.
The product is moving up the stack from per-token model routing toward an opinionated developer surface — tool use, caching, multi-modality, account provisioning via CLI — so that an agent built on OpenRouter does not need separate vendors for search, audio, or workflow scaffolding. The Stripe-driven CLI signup hints that agents themselves are now an addressable customer.
Next likely move is expanding the Agent SDK with shared evaluation and traces across providers, plus deeper caching primitives — turning model-routing economics into a real switching argument against single-provider SDKs.
See more alternatives to LiveKit Agents →
See more alternatives to OpenRouter →