KAGENTXINTEL TERMINAL

Speko (YC S26) – OpenRouter for Voice AI

A multi-model evaluation and routing layer for voice agent development teams, selecting STT, LLM, and TTS combinations based on language, region, and cost/delay/accuracy targets.

Who it is for: Teams needing to continuously select and replace STT, LLM, and TTS in multilingual production voice agents; developers using LiveKit, Pipecat, or self-built voice agent infrastructure compatible with OpenAI API; teams wanting to retain their own infrastructure but reduce the cost of model evaluation and vendor switching.

Positioning

A multi-model evaluation and routing layer for voice agent development teams, selecting STT, LLM, and TTS combinations based on language, region, and cost/delay/accuracy targets.

  • Product stage: Early commercialization stage; the official website notes Y Combinator support, HN page shows as Launch HN, but absolute release date and business scale remain unverified.

Core features

  • Routing by language and target: Filter and select models based on language, region, accuracy, delay, cost, or balance targets.
  • Multi-model benchmark evaluation: Evaluate multiple speech models by language and date, and publish evaluation boards.
  • Unified gateway access: Connect multiple vendors through a unified base URL, key, and OpenAI API-compatible interface.
  • Session prefetch and connection failure switching: Prefetch signed session plans and attempt candidate vendors if connection setup fails.

Target users

  • Teams needing to continuously select and replace STT, LLM, and TTS in multilingual production voice agents: A multi-model evaluation and routing layer for voice agent development teams, selecting STT, LLM, and TTS combinations based on language, region, and cost/delay/accuracy targets.
  • Developers using LiveKit, Pipecat, or self-built voice agent infrastructure compatible with OpenAI API: A multi-model evaluation and routing layer for voice agent development teams, selecting STT, LLM, and TTS combinations based on language, region, and cost/delay/accuracy targets.
  • Teams wanting to retain their own infrastructure but reduce the cost of model evaluation and vendor switching: A multi-model evaluation and routing layer for voice agent development teams, selecting STT, LLM, and TTS combinations based on language, region, and cost/delay/accuracy targets.

Pricing

  • Hosted router and hosted key charging; gateway and BYOK free. · Specific pricing, billing units, free quotas, and margin structure are not disclosed.: Hosted services billed by usage, minutes, requests, or other metrics; hosted key markup relative to supplier costs

Verdict

Speko's problem definition is clear, and the combination of unified access, language-based evaluation, and production routing forms a relatively complete product loop. As an early-stage product for voice agent teams, it has clear value. However, the current materials are insufficient to prove that evaluation advantages are reproducible, hosted services can form stable commercial scale, or moats exist.

  • Strength: Transferring multilingual model selection from one-time manual assessments to callable routing capabilities; simultaneously providing OpenAI API-compatible access, BYOK, and local gateways to reduce migration resistance; the official website and HN both emphasize public, date-based evaluation results, which help build trust in selection.
  • Limitation: There are clear gaps in evaluation coverage, with some models having only English data; pricing, paying customers, revenue, retention, and margin are all unverified; independent user feedback samples are very limited, and growth and customer cases mainly come from product-side self-description.

How it delivers value

  • Task submission: Developers submit language, region, and accuracy, delay, cost, or balance targets. → Developers submit language, region, and accuracy, delay, cost, or balance targets.
  • Understanding and decision-making: The router filters candidate models from evaluated ones and returns vendor, model name, and score. → The router filters candidate models from evaluated ones and returns vendor, model name, and score.
  • Execution and delivery: The unified gateway establishes a voice session and attempts candidate vendors if connection setup fails. → The unified gateway establishes a voice session and attempts candidate vendors if connection setup fails.
  • Feedback and reuse: Teams can re-evaluate models based on new dated evaluation results without re-implementing each vendor's interface. → Teams can re-evaluate models based on new dated evaluation results without re-implementing each vendor's interface.

Competition

Speko's differentiation is not just providing voice model APIs, but combining multilingual evaluation, full STT+LLM+TTS selection, and unified access.

  • vs OpenRouter: Wins: From current materials, Speko emphasizes the overall selection of STT, LLM, and TTS in voice agents and routing by language. Loses: HN commenters point out that there will be many competitors; this round has no independent evidence proving Speko's long-term leadership in coverage, quality, or price.
  • vs LiveKit Gateway: Wins: Speko's self-description focuses on continuous evaluation and selecting the right voice stack, rather than just connecting a gateway. Loses: This round did not read the LiveKit Gateway's direct page, so it's impossible to prove superiority in real-time session capabilities between the two.
  • vs Vapi: Wins: Speko claims teams can retain their own infrastructure and switch between models. Loses: Vapi is described by the product side as a hosted platform; self-built infrastructure and internal orchestration may increase adoption and operational costs.

Risks

  • Incomplete evaluation coverage: the official website states that 11 out of 23 models only measure English.: Incomplete evaluation coverage: the official website states that 11 out of 23 models only measure English.
  • Continuous changes in model, vendor, and language quality may increase evaluation maintenance costs as coverage expands.: Continuous changes in model, vendor, and language quality may increase evaluation maintenance costs as coverage expands.
  • Real-time voice links are sensitive to delay and session stability; gateway failures may directly affect calls.: Real-time voice links are sensitive to delay and session stability; gateway failures may directly affect calls.
  • Dependence on third-party model vendors; changes in vendor pricing, interfaces, and availability may affect product value.: Dependence on third-party model vendors; changes in vendor pricing, interfaces, and availability may affect product value.
  • Anonymous, content-free telemetry is enabled by default; enterprise customers may need further review.: Anonymous, content-free telemetry is enabled by default; enterprise customers may need further review.

Company

  • Stage: Early commercialization stage; the official website notes Y Combinator support, HN page shows as Launch HN, but absolute release date and business scale remain unverified.
  • Funding: Not disclosed

User voices

  • Positive: HN commenters find the product interesting and believe there is still unmet product space in voice agents.
  • Negative: HN commenters think there will be many competitors, indicating the need to prove the independence and continuous differentiation of the routing layer.
  • Requested: There is only one HN discussion page in this round, and the comment sample is not representative.
  • Requested: Founder's customer cases, usage growth, and evaluation methods belong to product-side self-description and should not be equated with independent user satisfaction.
  • Requested: Reddit, X, and independent reviews are unavailable in the specified context and cannot be used to infer overall reputation.

Sources

Updated 2026-08-18

Visit Speko (YC S26) – OpenRouter for Voice AI