FreeTTS REST API
REST/JSON API for text-to-speech synthesis, audio and SRT subtitle download, and voice listing. Uses x-api-key header auth. Endpoints: POST /api/v1/tts, GET /api/audio/{file_id}, GET /api/srt/{file_id}, GET /api/voices. Submitted 2026-08-28 from shubham@telenow.ai with a NAME ONLY -- no apis.json, no docs URL, no provider. telenow.ai is a HubSpot page unrelated to freetts.org, and nothing on freetts.org links the two, so this is a third-party submission. freetts.org itself is healthy and serves an llms.txt; no apis.json and no OpenAPI resolve. The gate's own research notes the backend proxies Microsoft Azure Neural TTS -- recorded as provenance, not as a policy problem: building a product on Azure TTS is that service's intended use, unlike the model relays refused this week, which documented redirecting first-party CLI clients. Verified 2026-08-28. ENRICHMENT PASS 2026-08-28: contract discovery ran against the API host root, the docs host and every well-known path and found no machine-readable contract. /openapi.json, /swagger.json, /openapi.yaml, /api-docs, /docs and /redoc all return the Next.js catch-all 404; /api/openapi.json, /api/v1/openapi.json, /api/docs, /api/redoc and /api/schema all return the API application's own JSON 404 {"detail":"Not Found"}, so the FastAPI-style app that serves this API has its interactive docs and schema routes disabled. No GraphQL, no MCP endpoint, no agent card, no WSDL, no .proto. The endpoint set is larger than first recorded: POST /api/v1/tts, POST /api/tts-pro (expressive styles, named only in llms.txt, existence confirmed by a live 405 on GET), GET /api/audio/{file_id}, GET /api/srt/{file_id}, GET /api/voices and an undocumented GET /api/health returning 200 {"status":"ok","timestamp":}. GET /api/voices is fully open - it returned 585,024 bytes and 1,410 voice objects with no credential. The /developers hero markets the API as "No Key Required" while the same page's FAQ, all four code samples and the live 401 ({"detail":"Missing x-api-key header"}) require an x-api-key header. Free-tier limits are published at three different values (10, 15 and 20 requests/minute) and the per-request character cap at two (1,000 and 5,000) across two of the provider's own pages, and no rate-limit response headers are emitted at all. The documented embed widget loader https://freetts.org/widget.js returns 404.