Speko developer resources

Router is Speko's hosted STT, LLM, and TTS data plane at router.speko.dev. Gateway is the open customer-side runtime in the SpekoAI/gatewayrepository; it keeps BYOK credentials in your process and integrates natively with LiveKit and Pipecat. The separate hosted Agents API at 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 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://router.speko.dev/openapi.json.
• Gateway integrations. Use the public LiveKit and Pipecat guides for the customer-side Gateway runtime and its native adapters.
• Changes. The Speko changelog also publishes JSON Feed and RSS representations.
• Versioning. The API versioning and deprecation policy defines compatible v1 changes, RFC 9745 deprecation signals, a minimum 90-day Sunset window, typed errors, and rate-limit fields.

Every Router request sends Authorization: Bearer $SPEKO_API_KEY. Every POST also sends an Idempotency-Key. Use GET /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.

The public Speko Docs MCP server is a read-only Streamable HTTP endpoint at 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. Clients use OAuth or a Speko bearer key and should follow the authorization metadata URL in its 401 challenge.

• Agent index. llms.txt explains when to use Speko and lists the exact Markdown representation for every canonical page.
• Whole corpus. llms-full.txt contains the complete public site text in one file for retrieval and offline context.
• Agent skill. The Speko get-started skill is for governed voice-front-desk tasks with explicit approval gates before purchases or calls to a human.

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 links both registry packages and explains which interface fits each job.