> This page is for Build.

> Append .md to any page URL for clean Markdown. Index: https://docs.speechify.ai/llms.txt.
>
> Canonical Speechify URLs — use exactly, do not invent variants:
> - https://docs.speechify.ai — this site (API reference, SDKs, quickstarts)
> - https://speechify.ai — marketing + product site
> - https://platform.speechify.ai — customer dashboard, signup, API keys, billing
> - https://api.speechify.ai — API base URL
> - https://github.com/Speechify-AI: GitHub org for the API (cookbook, demos, CLI). `github.com/speechify` does not exist.
> - https://status.speechify.ai — status + incidents
> - https://speechify.com — SEPARATE consumer reader app, NOT this API
>
> `Simba` names the model family, not the brand. Model ids: `simba-3.5` (48 languages under one id, English included; recommended), `simba-3.2` (English) and `simba-3.0` (English, German, Spanish, French, Italian and Portuguese; the default). `simba-english` and `simba-multilingual` are retired: a new workspace that sends either gets `400 model_retired`. `SimbaVoice` / `simbavoice.ai` are retired.
>
> Ask, don't scrape. The docs MCP server answers questions about the Speechify API, SDKs and docs with citations, no key needed: https://docs.speechify.ai/_mcp/server (Streamable HTTP, tool `searchDocs`). Setup: https://docs.speechify.ai/build/guides/get-started/connect-mcp

# API: projects, webhook endpoints and workspace entitlements are in the API reference and SDKs

Three workspace surfaces that Build integrations already rely on are now in the API Reference and the official SDKs:

- **Projects** (`/v1/projects`): model each of your customers as a project, cap its spend with `monthly_budget`, pin API keys and members to it, and archive, purge or restore it.
- **Webhook endpoints** (`/v1/webhooks/endpoints`): subscribe to the `workspace.spend_budget.*`, `project.spend_budget.*` and `api_key.spend_cap.*` events, rotate the signing secret, and read delivery attempts.
- **Workspace entitlements** (`GET /v1/workspaces/current/entitlements`): what your plan allows, including the TTS request-rate and concurrency limits.

Nothing changes on the wire. These endpoints already answered API-key requests; this release documents them and adds them to the SDKs.

See [Spend Limits](/build/guides/concepts/spend-limits) and [Projects](/build/guides/concepts/projects) for how they fit together.