> 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.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: watermark verification with no credential

A new endpoint answers whether a clip carries a Speechify watermark without any credential. `POST /v1/audio/watermark/verify` takes the same audio upload as `POST /v1/audio/watermark/detect` and returns a bare `{"watermarked": true|false}` — no key, no session, nothing to authenticate.

It is the API half of the public tool at [speechify.ai/detect](https://speechify.ai/detect), and it exists because California's AI Transparency Act (BPC 22757.2) requires a detection tool that is publicly accessible and invokable without visiting a website.

`verify` answers; `detect` measures. The new verb deliberately omits the confidence score its sibling returns — a public score is a gradient to optimise against. Keep using `POST /v1/audio/watermark/detect` with an API key when you want the score.

Because `verify` takes no credential, it is rate-limited per client address and draws on a shared platform budget, so expect `429` under sustained automated use. Nothing changes for an existing integration: `POST /v1/audio/watermark/detect`'s path, request and response are untouched.