Voice agent API vs voice AI SDK

An API runs the conversation for you. An SDK is how your app talks to it. Here is when to use each.

  • API runs the conversation on a managed backend
  • SDK is a client library (Python, TypeScript)
  • Frameworks are a third category: assemble your own stack

Definition

The terms get used interchangeably, but they name different things. A voice agent API is a service that runs the conversation on a managed backend. A voice AI SDK is a client library your application uses to call that service. One is the engine; the other is the steering wheel.

The API

The API is where the work happens. You send an agent configuration and, at call time, audio streams in and out along with structured events. Speech-to-text, the LLM, text-to-speech, and telephony all run behind that endpoint. You do not host or scale any of it.

The SDK

The SDK is a thin, typed wrapper around the API. SpeechifyAI ships Python (speechify-api) and TypeScript (@speechify/api) SDKs that read your API key from the environment and expose methods instead of raw HTTP. If you are in another language, you call the REST API directly and get the same behavior.

The framework option

There is a third category worth naming: orchestration frameworks. With those you assemble your own STT, LLM, and TTS and run the loop yourself. That is maximum control and maximum maintenance. An all-in API does the assembly for you and charges one rate, which is the right trade for most teams shipping to production.

How to choose

Pick the SDK if you are in Python or TypeScript and want less boilerplate. Pick the raw API for other languages or full request control. Pick a framework only if you genuinely need to own every layer. All three, in our case, sit on top of the same managed backend.

FAQ

Frequently asked questions

What is the difference between a voice agent API and a voice AI SDK?
A voice agent API runs the conversation for you on a managed backend: you send configuration and receive audio and events. A voice AI SDK is a client library your app uses to call that API from a browser, phone, or server. The API is the service; the SDK is the convenience wrapper around it.
When should I use the API directly versus the SDK?
Use the SDK when you are building in Python or TypeScript and want typed methods and less boilerplate. Use the raw REST API when you are in another language or need full control over the requests. Both talk to the same backend, so the choice is about developer experience, not capability.
How is this different from an orchestration framework?
Frameworks like open-source agent toolkits are a third category: you assemble your own speech-to-text, LLM, and text-to-speech and run the orchestration yourself. An all-in API does that assembly for you and bills it as one rate, trading some control for far less to build and maintain.

Start building

An API runs the conversation for you. An SDK is how your app talks to it. Here is when to use each.

Privacy preferences

Choose what we may store on this device. You can change this at any time from the footer.

Strictly necessary

Sign-in, security, load balancing, and remembering your privacy choices. These cannot be switched off.

Always on

Analytics

How the site is used in aggregate - which pages get read, where people get stuck - so we can improve it.

Marketing

Measures which campaigns bring people here, and lets us show relevant ads on other platforms.