> 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.2` (English, recommended) 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: Differentiated Rate Limits for Free and Paid Users

We've introduced differentiated rate limiting based on user plan type to ensure fair usage and optimal performance for all users.

### Rate Limits

| Plan Type | Rate Limit |
|-----------|------------|
| Free | 1 request/second |
| Paid | 20 requests/second |

### What This Means

- **Free users** are now subject to a lower rate limit of 1 request per second
- **Paid users** continue to enjoy the standard rate limit of 20 requests per second
- When rate limited, responses include a `Retry-After` header indicating when to retry

### Affected Endpoints

- `POST /v1/audio/speech`
- `POST /v1/audio/stream`

<Info>
  If you exceed the rate limit, you'll receive a `429 Too Many Requests` response.
  Check the `Retry-After` header for guidance on when to retry your request.
</Info>