Speko website screenshot

Speko

Speko is a voice-AI gateway - "one API for the whole voice stack." It continuously benchmarks speech-to-text, LLM, and text-to-speech providers and routes every call to the best provider for your language, latency, and cost intent, with transparent server-side failover. Developers ship voice agents in minutes over one REST API (no provider keys required, or bring your own), deploying to phone numbers, web widgets, or one-shot transcribe/synthesize/ complete calls. Speko is a Y Combinator (S26) company based in San Francisco, founded by Beknazar Abdikamalov. The platform advertises SOC 2 Type II, HIPAA, and GDPR posture and ships TypeScript and Python SDKs, a browser SDK, a LiveKit adapter, and a hosted MCP server.

Speko publishes 4 API contracts indexed on the APIs.io network, including Agents API, Providers API, Telephony API, and 1 more. Tagged areas include Voice, Voice AI, Speech-to-Text, Text-to-Speech, and LLM.

The Speko catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Speko’s developer surface includes documentation, API reference, getting-started guide, pricing, signup flow, engineering blog, support, and 18 more developer resources.

59.7/100 strong ▬ flat Agent 61/100 agent native Front door AI 4/6 moderate Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessPaid
1 published contract 1 MCP Servers 3 Agent Skills
VoiceVoice AISpeech-to-TextText-to-SpeechLLMTelephonyAPI GatewayConversational AIDeveloper ToolsAI Infrastructure

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the AI & Biometrics regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Speko It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/speko/"><img src="https://apis.io/badge/speko/card.svg" alt="Speko on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
  • Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter
  • Well-Known Catalog +4 pts — common[].type includes WellKnown, APICatalog, or api-catalog
  • Consent & Bot Identity +3 pts — common[].type includes AIPREF, ContentSignal, WebBotAuth, or HTTPMessageSignatures
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/speko/apis.yml: open an issue on github.com/api-evangelist/speko to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (verified)
measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)
measured — observed by APIs.io (published)

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Speko Agents API

The Agents API from Speko — 2 operation(s) for agents.

Speko Providers API

The Providers API from Speko — 1 operation(s) for providers.

Speko Telephony API

The Telephony API from Speko — 22 operation(s) for telephony.

Speko Voice API

The Voice API from Speko — 8 operation(s) for voice.

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Speko Agents API

OPEN COLLECTION

Speko Agents Voice API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Speko MCP Server

Remote MCP server at mcp.speko.ai over HTTP.

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Speko API pricing

Prices published by Speko, read 2026-10-07 from speko.ai/pricing.

PlanPrice
Router +5% on the provider's rate
Includes: Speech-to-text, LLM, TTS: The provider's published rate; Measured selection and pre-response failove
Speko infra $0.09 per minute
Includes: Speech-to-text, LLM, TTS included; Measured selection and pre-response failover; Public preview; Ema
Enterprise Custom locked for the term
Includes: Included STT/LLM/TTS; plus deployment reviews; access by contract; dedicated support; SLA in the con
Signup credit $10 in signup credit applies to every account.

Plan details, limits and sources →

Billed by: cent on provider rate · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Speko Plans Pricing

4 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Speko

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Speko Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Speko Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Speko API Rules

60 rules · 48 errors 10 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Speko Openapi Overlay

3 actions · update · speko-openapi-original.json

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Speko Authentication

http · 1 scheme

SECURITY

Speko Domain Security

TLSv1.3

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Speko Agentic Access

40 operations · 22 acting · 1 human-in-the-loop

40 operations · 22 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: speko
name: Speko
description: Speko is a voice-AI gateway - "one API for the whole voice stack." It continuously benchmarks speech-to-text,
  LLM, and text-to-speech providers and routes every call to the best provider for your language, latency, and cost intent,
  with transparent server-side failover. Developers ship voice agents in minutes over one REST API (no provider keys required,
  or bring your own), deploying to phone numbers, web widgets, or one-shot transcribe/synthesize/ complete calls. Speko is
  a Y Combinator (S26) company based in San Francisco, founded by Beknazar Abdikamalov. The platform advertises SOC 2 Type
  II, HIPAA, and GDPR posture and ships TypeScript and Python SDKs, a browser SDK, a LiveKit adapter, and a hosted MCP server.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://speko.ai/favicon.ico
url: https://raw.githubusercontent.com/api-evangelist/speko/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- y-combinator
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
tags:
- Voice
- Voice AI
- Speech-to-Text
- Text-to-Speech
- LLM
- Telephony
- API Gateway
- Conversational AI
- Developer Tools
- AI Infrastructure
tags_raw:
- Voice
- Voice AI
- Speech to Text
- Text to Speech
- LLM
- Telephony
- API Gateway
- Conversational AI
- Developer Tools
- AI Infrastructure
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: speko:speko-agents-api
  name: Speko Agents API
  description: The Agents API from Speko — 2 operation(s) for agents.
  humanURL: https://docs.speko.dev/api-reference/introduction
  baseURL: https://api.speko.dev
  tags:
  - Agents
  properties:
  - type: OpenAPI
    url: openapi/speko-agents-api-openapi.yml
  - type: Authentication
    url: authentication/speko-authentication.yml
  - type: ErrorCatalog
    url: errors/speko-problem-types.yml
  - type: Conventions
    url: conventions/speko-conventions.yml
  - type: Idempotency
    url: conventions/speko-conventions.yml
  - type: DataModel
    url: data-model/speko-data-model.yml
  - type: Webhooks
    url: asyncapi/speko-webhooks.yml
- aid: speko:speko-providers-api
  name: Speko Providers API
  description: The Providers API from Speko — 1 operation(s) for providers.
  humanURL: https://docs.speko.dev/api-reference/introduction
  baseURL: https://api.speko.dev
  tags:
  - Providers
  properties:
  - type: OpenAPI
    url: openapi/speko-providers-api-openapi.yml
  - type: Authentication
    url: authentication/speko-authentication.yml
  - type: ErrorCatalog
    url: errors/speko-problem-types.yml
  - type: Conventions
    url: conventions/speko-conventions.yml
  - type: Idempotency
    url: conventions/speko-conventions.yml
  - type: DataModel
    url: data-model/speko-data-model.yml
  - type: Webhooks
    url: asyncapi/speko-webhooks.yml
- aid: speko:speko-telephony-api
  name: Speko Telephony API
  description: The Telephony API from Speko — 22 operation(s) for telephony.
  humanURL: https://docs.speko.dev/api-reference/introduction
  baseURL: https://api.speko.dev
  tags:
  - Telephony
  properties:
  - type: OpenAPI
    url: openapi/speko-telephony-api-openapi.yml
  - type: Authentication
    url: authentication/speko-authentication.yml
  - type: ErrorCatalog
    url: errors/speko-problem-types.yml
  - type: Conventions
    url: conventions/speko-conventions.yml
  - type: Idempotency
    url: conventions/speko-conventions.yml
  - type: DataModel
    url: data-model/speko-data-model.yml
  - type: Webhooks
    url: asyncapi/speko-webhooks.yml
- aid: speko:speko-voice-api
  name: Speko Voice API
  description: The Voice API from Speko — 8 operation(s) for voice.
  humanURL: https://docs.speko.dev/api-reference/introduction
  baseURL: https://api.speko.dev
  tags:
  - Voice
  properties:
  - type: OpenAPI
    url: openapi/speko-voice-api-openapi.yml
  - type: Authentication
    url: authentication/speko-authentication.yml
  - type: ErrorCatalog
    url: errors/speko-problem-types.yml
  - type: Conventions
    url: conventions/speko-conventions.yml
  - type: Idempotency
    url: conventions/speko-conventions.yml
  - type: DataModel
    url: data-model/speko-data-model.yml
  - type: Webhooks
    url: asyncapi/speko-webhooks.yml
common:
- type: Plans
  url: plans/speko-plans-pricing.yml
- type: Website
  url: https://speko.dev
- type: Overlay
  url: overlays/speko-openapi-overlay.yaml
- type: DeveloperPortal
  url: https://docs.speko.dev
- type: Documentation
  url: https://docs.speko.dev
- type: APIReference
  url: https://docs.speko.dev/api-reference/introduction
- type: GettingStarted
  url: https://docs.speko.dev/quickstart
- type: Pricing
  url: https://speko.ai/pricing
- type: SignUp
  url: https://platform.speko.dev/sign-in
- type: TermsOfService
  url: https://speko.ai/terms-of-service
- type: PrivacyPolicy
  url: https://speko.ai/privacy-policy
- type: Blog
  url: https://speko.ai/blog
- type: GitHubOrganization
  url: https://github.com/SpekoAI
- type: StatusPage
  url: https://status.speko.ai
- type: Support
  url: mailto:founders@speko.ai
- type: MCPServer
  url: mcp/speko-mcp.yml
- type: Packages
  url: packages/speko-packages.yml
- type: SDKs
  url: packages/speko-packages.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Lifecycle
  url: lifecycle/speko-lifecycle.yml
- type: Conformance
  url: conformance/speko-conformance.yml
- type: Compliance
  url: https://speko.ai/
- type: Authentication
  url: authentication/speko-authentication.yml
- type: AgenticAccess
  url: agentic-access/speko-agentic-access.yml
- type: DomainSecurity
  url: security/speko-domain-security.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 17
  pass: local-v1

Speko API — frequently asked questions

Does Speko have an API?

Yes. APIs.io lists 4 APIs from Speko, including Speko Agents API, Speko Providers API and Speko Telephony API, and 1 more.

Is there an OpenAPI specification for the Speko API?

Yes. APIs.io indexes 4 OpenAPI specifications for Speko, each linked for download from this page.

How do I authenticate with the Speko API?

Speko documents its authentication (http · 1 scheme). The details are profiled on APIs.io as Speko Authentication.

How much does the Speko API cost?

Speko publishes its prices; its Router plan is +5% on the provider's rate as of 2026-10-07. APIs.io lists 4 pricing plans for Speko, with each plan's price, limits and inclusions under Pricing on this page.

Does Speko have an MCP server?

Yes. APIs.io lists 1 MCP server for Speko: Remote MCP server at mcp.speko.ai over HTTP.

Is the Speko API ready for AI agents?

Speko has a Kin Score of 59.7 out of 100 (strong) and an Agent Readiness score of 61.0 (agent-native), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/speko"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/speko/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/speko/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.