Recent submissions

Comment · 2 months ago
not really counter-positioned, they are one of the providers we route to. elevenlabs sells models - voices, stt, and their agent platform on top of them. we don't sell any models: we measure all of them (elevenlabs included, their scribe is near the top of our stt board) and route each request to whatever wins for your language and constraints. so for them the best outcome is that you use their models; for us the best outcome is that you use the right one. sometimes that is the same thing.
Comment · 2 months ago
i don't have a thesis on voice as a form factor for search. the demand we serve already exists: businesses answer phones. receptionists, outbound campaigns, clinic front desks and these calls happen at scale today, and the teams running them are the ones picking speech models. whether voice wins new interfaces is a separate bet
Comment · 2 months ago
thanks! yes, some of them do, cuz speed is a per-provider capability, not universal. And, you can see it in the gateway code (minimax, hume, xai tts adapters all handle a speed param). that unevenness is actually a routing constraint by itself: "voices that support rate control" narrows the candidate list the same way language or latency does. and agree on the voice modes, the gap between the demo and a dependable agent is exactly why we started this. what are you building with it?
Comment · 2 months ago
People who built or building voice agents immediately get this.

openrouter is the openrouter for audio models.

the conflation is "audio models" vs "voice ai", and the mental model that untangles it: think batch requests. text in, audio out (streamed, even). audio in, transcript out.

three questions inside the word "router":

1 - what gets picked: a model/voice, a provider of the same model, or the whole stack (stt + llm + tts) per call

2 - where it lives: an external http gateway, the agent platform (vapi/retell/livekit configs), or inside the live session

3 - when: session start, or mid-call

a voice agent is not a batch request. it's a live duplex session: turn-taking, barge-in, telephony legs, session state. the latency physics diverge too: a middleman hop in the media path is paid once by a batch request and on every conversational turn of a live call, so the media path wants a direct connection to the provider. a gateway that terminates at http can route the requests inside a call; it can't route the call.

Comment · 2 months ago
yes, it does support, when you are creating an api key, you can point out narration or transcription use case, then you will be able to see. let me know how it goes or what use cases are thinking of for non-realtime models?
Comment · 2 months ago
looks cool, checking it out!
Comment · 2 months ago
exactly, we see the same thing, around 95% cases are still cascaded, even tho STS has been improving a lot
Comment · 2 months ago
Synthetic-data fine-tuning is the other credible answer to domain vocabulary. Curious whether you re-benchmark the fine-tune when new base models ship?
Comment · 2 months ago
What purrcat259 said, and I think that the page should explain it, we will add a tooltip.

for some languages CER is more relevant than WER. Thai and Mandarin have no word boundaries, so we score them by character, and Japanese gets a reading-based CER.

Comment · 2 months ago
Comment · 2 months ago
Comment · 2 months ago
cool app, and agreed that on-device keeps eating the single-user cases, we are seeing dictation and translation are exactly where local models shine. We benchmark the open models on the same boards as the hosted ones, but there are still a few: https://benchmarks.speko.ai/open.

production phone agents are a different shape today: the call terminates server-side, three models plus turn-taking under one latency budget, and per-language quality still swings a lot from our tests

Comment · 2 months ago
Comment · 2 months ago
Yes, on the hosted side (agents platform): full sessions come with VAD and turn-taking handled - we set them up and tune them for your use case, so that is the closest thing to conversation in a box. If you run your own orchestration, the gateway is just the routing layer and turn-taking stays in your framework - in our own stack we run Pipecat's Smart Turn in-process and tune the commit threshold on real calls. We also share our benchmarks here: https://benchmarks.speko.ai/turntaking

On fast dumb models answering while a smarter one takes over: we are experimenting with exactly that split - a small fast model holds the conversation while a larger one works behind it. Today it runs as two pinned routes, not one packaged API. Most turns in a phone call do not need a frontier model, and the fastest models on our LLM board are all small, so this is where routing earns its keep. We publish benchmarks on LLMs here: https://benchmarks.speko.ai/llm

Comment · 2 months ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton