One API for the voice stack
Speko positions the Router as a hosted, provider-neutral runtime for speech workflows, combining STT, LLM, and TTS behind one API surface.
Speko is a voice AI router that benchmarks speech models by language and routes STT, LLM, and TTS through one API. It also offers a packaged infrastructure option and an enterprise contract path.
Speko is a router for voice AI that presents itself as a hosted, provider-neutral STT, LLM, and TTS data plane. The homepage says it wires every speech model into one API and adds typed contracts and managed routing at router.speko.dev.
Its public site is centered on model selection and routing for voice applications. Speko benchmarks speech models language by language, then shows how those models compare on accuracy and cost across stages such as speech-to-text, LLM, text-to-speech, and speech-to-speech.
The pricing page separates the product into three paths: Router, Speko infra, and Enterprise. Router is in public preview and adds measured selection and pre-response failover on top of provider rates; Speko infra bundles the three voice-model legs into a single per-minute price; Enterprise is contract-based with deployment reviews and committed monthly minimums.
Overall, Speko is aimed at teams that need to choose among multiple speech providers and want that decision to be guided by benchmarks, routed through a single interface, and packaged with a clearer commercial boundary than stitching providers together manually.
Speko positions the Router as a hosted, provider-neutral runtime for speech workflows, combining STT, LLM, and TTS behind one API surface.
The homepage says models are benchmarked language by language, so selection can reflect how a model performs in the user’s language rather than relying on a single English ranking.
The site presents routing as measured selection with pre-response failover, which suggests the product can choose among providers before a response is sent.
The homepage references typed contracts and public OpenAPI and AsyncAPI contracts for the hosted Router, which points to a formal integration interface for automated clients.
The Gateway section shows native integrations for LiveKit and Pipecat, plus support for provider-direct streaming and local BYOK credentials.
The homepage includes benchmark boards for speech-to-text, LLM, text-to-speech, and speech-to-speech, making model comparison part of the product workflow.
Use Speko when a product needs to route speech traffic across multiple providers and choose models based on language-specific benchmark results rather than a single global ranking.
Use the Router when you want one hosted interface for STT, LLM, and TTS without wiring each provider separately, especially if your application already treats those stages as a pipeline.
Use the Gateway integrations when building with LiveKit or Pipecat and you want provider-direct streaming plus optional Speko-managed routes in the same setup.
Use Enterprise when procurement or operations require deployment reviews, contract-based access, dedicated support, or a committed monthly minimum.
Speko provides a router for voice AI that connects speech models into one API. The homepage describes it as a hosted, provider-neutral STT, LLM, and TTS data plane with typed contracts and managed routing.
The pricing page separates three commercial paths: Router, Speko infra, and Enterprise. Router is public preview and adds managed routing on top of provider rates; Speko infra bundles speech-to-text, LLM, and TTS into a per-minute price; Enterprise is by contract with deployment reviews and a committed monthly minimum.
The homepage says the Router is available at router.speko.dev and can be used through public OpenAPI and AsyncAPI contracts. It also shows native Gateway integrations for LiveKit and Pipecat, plus an MCP endpoint for Claude or Cursor.
The benchmark tables on the homepage compare models by language and by stage, including speech-to-text, LLM, and text-to-speech. The pricing page also notes that routing includes measured selection and pre-response failover.
The site does not present a full integration reference on the pages provided, so setup details such as authentication flow, SDK coverage, and endpoint schemas should be confirmed in the docs before implementation.
AakarDev AI helps teams manage AI provider access, project-level setups, logs, and analytics from one dashboard. It supports BYOK workflows and lists providers including OpenAI, Google Gemini, Anthropic, Groq, Mistral AI, and Perplexity AI.
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repositories and verifies changes with the real compiler, debugger, sanitizers, and tests before showing a diff. It offers a free tier plus paid plans, with editor connectors and zero-retention handling described in the source.
CreateOS Sandbox is an isolated compute environment for running code and agent workloads inside Firecracker micro-VMs. It is designed for workflows that need machine-level isolation, private networking between sandboxes, and programmatic control through SDK, CLI, or MCP.
hob is an independent workspace for coding agents that keeps agent sessions, terminals, history, and follow-up work organized around the tools and providers you already use. It is aimed at developers who want local control over routing, history, and workspace structure rather than a bundled model stack.
Ably Chat is a chat API platform for building custom realtime chat applications. It supports room-based messaging, typing indicators, presence, reactions, and message updates, with usage-based pricing options for different deployment stages.
Wallie is an open-source AI streamer that watches your screen, hears chat, and generates live commentary in a configurable persona. It runs locally on your machine with your own keys and is aimed at faceless content, autonomous streams, and real-time reactions.