speko.ai valid

Speko

Speko operates the hosted Router for managed STT, LLM, and TTS routing and publishes the open customer-side Gateway for provider-direct voice workloads.

For agents: Hosted Speko Router for managed STT, LLM and TTS routing, an open Gateway, voice AI benchmarks, and a documented Router API for voice agents.

voice aispeech-to-texttext-to-speechllm routingvoice agent infrastructure

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T03:32:12.999Z. Cached copy · Source on speko.ai

# Speko

> Speko operates the hosted Router for managed STT, LLM, and TTS routing and publishes the open customer-side Gateway for provider-direct voice workloads.

- Console: https://platform.speko.ai
- Hosted Router: https://router.speko.dev
- Router OpenAPI: https://speko.ai/openapi.json
- Router AsyncAPI: https://speko.ai/asyncapi.json
- RFC 9727 API catalog: https://speko.ai/.well-known/api-catalog
- Agentic Resource Discovery catalog: https://speko.ai/.well-known/ai-catalog.json
- Authentication and OAuth discovery: https://speko.ai/auth.md
- Router versioning and deprecation policy: https://speko.ai/developers/versioning
- Open customer-side Gateway: https://github.com/SpekoAI/gateway
- Hosted Agents API: https://api.speko.dev
- Public docs MCP (no authentication): https://speko.ai/.well-known/mcp
- Operational MCP (OAuth or bearer key): https://mcp.speko.ai/mcp
- Official CLI: https://speko.ai/developers/cli
- Benchmarks: https://benchmarks.speko.ai/
- Whole public-site corpus: https://speko.ai/llms-full.txt
- Router and Gateway scoped index: https://speko.ai/docs/llms.txt
- Developer-resource scoped index: https://speko.ai/developers/llms.txt
- Changelog feed (JSON Feed 1.1): https://speko.ai/changelog.json
- Changelog feed (RSS 2.0): https://speko.ai/changelog.xml

## When to use Speko

Use the hosted Router when an application wants Speko to operate a managed,
provider-neutral STT, LLM, or TTS data plane with typed requests, typed
responses, explicit route metadata, idempotent writes, and normalized errors.
Use the open Gateway when a LiveKit or Pipecat workload needs provider-direct
streaming, local BYOK credential custody, or a mixture of local and
Speko-managed routes. Use the hosted Agents API when the job is to create and
operate agents, sessions, phone numbers, or calls. These are distinct product
boundaries.

Use the public docs MCP at https://speko.ai/.well-known/mcp when an agent needs Speko
documentation without account access. Use https://mcp.speko.ai/mcp only for
authenticated account data or actions. Do not use Router as a hostname
replacement for an OpenAI SDK: Router has its own public OpenAPI and AsyncAPI
contracts.

## Hosted Router

Base URL: https://router.speko.dev

Authenticated operations send:

```text
Authorization: Bearer $SPEKO_API_KEY
```

Every POST and WebSocket upgrade also sends a caller-generated
`Idempotency-Key`. Reuse a key only for a byte-identical retry.

HTTP operations:

```text
GET  /openapi.json
GET  /asyncapi.json
GET  /v1/models
…

Related sites

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=speko.ai · GET /v1/domain/speko.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for speko.ai:
1. POST https://agentwebmap.com/v1/sites/speko.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://speko.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/speko.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/speko.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.