---
title: "Speko developer resources"
description: "Speko Router, Gateway, Agents API, OpenAPI, framework guides, MCP, CLI, and machine-readable discovery resources in one place."
canonical: "https://speko.ai/developers"
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.

# Speko developer resources

Developers

Speko Router, Gateway, Agents API, OpenAPI, framework guides, MCP, CLI, and machine-readable discovery resources in one place.

## Choose the right Speko surface

**Router** is Speko's hosted STT, LLM, and TTS data plane at [relay.speko.dev](https://relay.speko.dev).**Gateway** is the open customer-side runtime in the[SpekoAI/gateway](https://github.com/SpekoAI/gateway)repository; it keeps BYOK credentials in your process and integrates natively with LiveKit and Pipecat. The separate hosted**Agents API** at[api.speko.dev](https://api.speko.dev) owns agents, sessions, phone numbers, and calls. They solve different jobs and do not share an OpenAI-compatible facade.

- **Router quickstart.** The[native Router docs](https://speko.ai/docs) show model discovery, STT, LLM, and TTS calls with typed request and response bodies.
- **OpenAPI.** The canonical Router HTTP contract is served without authentication at[https://relay.speko.dev/openapi.json](https://relay.speko.dev/openapi.json).
- **Gateway integrations.** Use the public[LiveKit](https://speko.ai/docs/livekit) and[Pipecat](https://speko.ai/docs/pipecat) guides for the customer-side Gateway runtime and its native adapters.
- **Changes.** The[Speko changelog](https://speko.ai/changelog) also publishes[JSON Feed](https://speko.ai/changelog.json) and[RSS](https://speko.ai/changelog.xml) representations.
- **Versioning.** The[API versioning and deprecation policy](https://speko.ai/developers/versioning) defines compatible v1 changes, RFC 9745 deprecation signals, a minimum 90-day Sunset window, typed errors, and rate-limit fields.

## Call Router directly

Every Router request sends`Authorization: Bearer $SPEKO_API_KEY`. Every POST also sends an `Idempotency-Key`. Use[GET /v1/models](https://relay.speko.dev/v1/models) to discover currently routable models and their capabilities. Use`routing: { mode: "auto", objective: "balanced" }`for managed selection, or provide an explicit provider and model. Router is a native contract, not a hostname replacement for an OpenAI SDK.

## Connect an agent

The public Speko Docs MCP server is a read-only Streamable HTTP endpoint at[https://speko.ai/.well-known/mcp](https://speko.ai/.well-known/mcp). It requires no authentication: initialize the connection, list resources, read `spekoai://docs/index`, and then open the matching documentation resource rather than guessing a page or tool name.

Account data and write tools remain on the protected operational MCP endpoint at[https://mcp.speko.ai/mcp](https://mcp.speko.ai/mcp). Clients use OAuth or a Speko bearer key and should follow the authorization metadata URL in its 401 challenge.

- **Agent index.** [llms.txt](https://speko.ai/llms.txt) explains when to use Speko and lists the exact Markdown representation for every canonical page.
- **Whole corpus.**[llms-full.txt](https://speko.ai/llms-full.txt) contains the complete public site text in one file for retrieval and offline context.
- **Agent skill.** The[Speko get-started skill](https://speko.ai/.well-known/agent-skills/get-started/SKILL.md) is for governed voice-front-desk tasks with explicit approval gates before purchases or calls to a human.

## Use the official CLI

Speko publishes first-party command-line packages on npm. Use`npx @spekoai/mcp-calls init` for the disclosed agent-call setup flow, or `npx @spekoai/mcp` as a local stdio bridge when an MCP client cannot connect to Streamable HTTP directly. The[Speko CLI guide](https://speko.ai/developers/cli) links both registry packages and explains which interface fits each job.