---
title: "Changelog"
description: "Dated Speko API, model, SDK, console, and documentation changes, with migration actions and effective dates for breaking, deprecated, and retired updates."
canonical: "https://speko.ai/changelog"
last-updated: "2026-08-24"
---

> ## Speko page index
> The complete index of every page on this site is at: https://speko.ai/llms.txt
> Read it before exploring further. It lists the exact Markdown URL for every canonical HTML page.

# Changelog

Product updates

Dated API, model, SDK, console and documentation changes, with the migration action each one needs.

2 entries

[RSS](https://speko.ai/changelog.xml) [JSON](https://speko.ai/changelog.json)

<a id="relay-contract-discovery"></a>

Aug 24, 2026 Improved Available

Router Gateway API

## Router publishes its canonical machine-readable contract

The hosted Router now serves the Gateway-owned OpenAPI 3.1 document at /openapi.json and returns typed JSON for unknown routes and unsupported methods.

- GET https://router.speko.dev/openapi.json is public and returns the exact normative relayapi OpenAPI mirror embedded from the public Gateway repository.
- Unknown paths return route_not_found with HTTP 404. Known paths called with the wrong method return method_not_allowed with HTTP 405 and an Allow header.
- Every public Router response advertises the default edge quota through RateLimit-Policy. Application-generated 429 responses also include Retry-After and the normalized error envelope.
- The contract documents the stable /v1 compatibility policy, RFC 9745 deprecation signal, migration link, and minimum 90-day Sunset notice.

**Action:** No request migration is required. Agents and code generators should discover the Router contract from https://speko.ai/openapi.json or https://router.speko.dev/openapi.json instead of guessing routes.

[Router OpenAPI](https://router.speko.dev/openapi.json) [Versioning policy](https://speko.ai/developers/versioning)

<a id="gateway-public-runtime"></a>

Aug 24, 2026 Added Available

Gateway LiveKit Pipecat

## Gateway is the open customer-side voice runtime

Speko Gateway provides one local streaming protocol across voice providers, native LiveKit and Pipecat integrations, and local BYOK credential custody.

- Gateway runs in the customer workload and can call voice providers directly while keeping BYOK credentials inside the Gateway process.
- The public image ships native LiveKit and Pipecat integrations for streaming STT and TTS, interruption handling, usage, and timing events.
- Gateway can combine provider-direct voice legs with Speko-managed routes. The hosted Router remains a separate Speko-operated data plane at router.speko.dev.
- The public relayapi package in the Gateway repository is the canonical HTTP, SSE, and WebSocket wire contract for hosted Router traffic.

**Action:** Choose Gateway for provider-direct or local-BYOK workloads. Choose Router for the hosted managed data plane; the two surfaces are complementary, not interchangeable.

[Gateway repository](https://github.com/SpekoAI/gateway) [LiveKit guide](https://speko.ai/docs/livekit) [Pipecat guide](https://speko.ai/docs/pipecat)