Cartesia Ink vs Inworld STT

Cartesia Ink 84

Read as a model, on the lines deepgram-stt, gladia-stt and cartesia-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The cartesia-mcp server, which has a speech_to_text tool, released 0.28.1 on 30 October 2026 with a bug fix, after 0.27.0 (20 October) and 0.28.0 (27 October). The model page still dates ink-2 and ink-preview 17 September 2026 (30). In the 90 days from 3 August the SDKs released 4.0.0, 4.0.1, 4.1.0 and 4.2.0 (14 August to 2 September) and the MCP server several releases, with changelog entries for August and September (10). The deprecations page gives dated sunsets, and Sonic-2, Sonic Turbo and sonic-3-2025-10-27 were sunset after 20 October 2026, announced in the July changelog. No minimum notice period is stated and no Ink model has been retired, read as cartesia-tts is on the same page (5 of 10). The changelog has speech-to-text entries in May, June, July and September 2026, dated by month only, and no October entry (11 of 15). The Python SDK repository had 4 open issues on 9 October, per that check, not re-read on 1 November since GitHub's pages answered 403 (5 of 10). Official cartesia and @cartesia/cartesia-js SDKs at 4.2.0 (2 September 2026), generated for API version 2026-08-14 (15). CI workflows, release automation and lock files in both SDK repositories, with dependency updates merged on 23 October (8 of 10). 30 + 10 + 5 + 11 + 5 + 15 + 8 = 84.

Inworld STT 41

Read as a model. No public STT changelog. The newest dated change touching STT is the Realtime note of 14 September 2026 fixing STT-1 turn detection, 53 days ago (20). The CLI, which carries the STT command and MCP tool, shipped 1.4.0 to 1.5.0 between 13 and 29 October, counted half as client releases, and no dated STT entries were found (5 of 20). Discord and support@inworld.ai, with no evidence of answers read (6 of 15). No official STT SDK; the CLI is current (5 of 15). CLI on npm under MIT, current, CI not read (5 of 10). Total 41.

Cartesia Ink 89

Model reading. The docs index links an OpenAPI file (latest.yml) and AsyncAPI files for the WebSocket endpoints, and each reference page embeds its part of them (25). llms.txt with a Markdown twin of every page (10). The comparison page says which of the three endpoints to use and when, and the turn detection guide explains each event and threshold (18 of 20). The AsyncAPI definition has enums for encoding and cartesia_version, minimum and maximum values on the four turn settings and required fields marked. model is a plain string on the auto endpoint (13 of 15). Example scripts for each endpoint in Python and TypeScript and an errors page with nine codes. model_sunsetted appears on the deprecations page and not in that table, and the docs say a wrong encoding or sample_rate might not return an error (11 of 15). Dated API versions through the Cartesia-Version header and a changelog grouped by month with no day dates (12 of 15).

Inworld STT 54

No OpenAPI or other machine-readable file. The usual spec paths redirect, and the reference pages are Markdown (0). llms.txt, Markdown twins and a docs MCP server (10). Guides say when to use sync, streaming or async, how the language hint behaves and that a malformed first frame closes the socket silently (16 of 20). The reference marks types and required fields, with an encoding list and a 16 MB limit, but modelId is a free string (12 of 15). Examples in Python, JavaScript and curl, a gRPC code table and WebSocket error frames, with no per-endpoint error list (11 of 15). Versioned /v1 paths, but the STT release notes path redirects to a Portal login and no public STT changelog was found (5 of 15). Total 54.

Cartesia Ink 74

API reading, as for the other speech-to-text listings. Turn events carry a cumulative transcript that is never revised, so an agent reads one turn.end a turn, and word timestamps are opt-in on the manual and batch endpoints (20 of 25). There is nothing to page through. Batch takes a file of any length without client chunking, keyterms steer vocabulary, and there is no diarisation or subtitle output (12 of 20). Errors are structured JSON with error_code, title, message, request_id and an optional doc_url on API version 2026-03-01 and later (17 of 20). Transcription holds no state to duplicate and the SDKs retry failed HTTP calls. A realtime session cannot be resumed, and nothing on reconnecting was found (12 of 20). Realtime needs model, encoding, sample_rate and the version, turn settings have documented defaults, and there are official Python and TypeScript SDKs. Realtime accepts raw PCM only (13 of 15).

Inworld STT 56

API reading of the checklist. Voice Profile, word timestamps and diarisation are opt-in, and responses carry a usage block (18 of 25). No lists to page. Async jobs return an operation to poll (8 of 20). Errors carry a numeric gRPC code and message on both endpoints, but a malformed first message closes the socket with 1005 and no frame (12 of 20). Sync calls are stateless and async calls return an operation, with no idempotency key, and empty transcripts and add-ons are billed (10 of 20). A call needs a model, an encoding and the audio. No STT SDK was found, only the CLI and its MCP server and REST examples (8 of 15). Total 56.

Cartesia Ink 47

Model reading. Standard keys (sk_car_...) and admin keys are separate types that are not interchangeable, and a server can mint an access token with an stt grant that lasts at most one hour. That token travels in the access_token query parameter on WebSockets, the API key itself goes in a header, and no key limited to speech-to-text was found. The STT WebSocket definition, re-read on 1 November, lists access_token in the query as a security scheme. The checklist takes 10 off for a secret that can travel in a URL query string as a documented option, and this run takes the full 10 for short-lived OAuth tokens in ?access_token= on every Google API listing, so the earlier 5 is brought into line (26, less 10, 16 of 30). The terms, last revised 14 June 2024, say inputs, outputs and interactions may be used to train models unless otherwise agreed, with an opt-out form in the Playground's data controls (5 of 20). Zero data retention covers STT audio and transcripts and is limited to the Enterprise plan. No retention period for other plans was found, and the DPA gives 180 days for deletion after termination (5 of 15). Credit usage and key metadata are readable through admin endpoints. No audit log was found (7 of 15). security.txt is valid until 3 October 2027 with a contact and a policy link to the trust centre. The docs and pricing page state SOC 2 Type II, HIPAA and PCI-DSS. The trust centre is drawn by script and was not read, and no bug bounty was found (14 of 20). 16 + 5 + 5 + 7 + 14 = 47.

Inworld STT 63

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Workspace API keys sent as Basic credentials, deleted to revoke, with separate keys per environment advised. The CLI mints read-only keys unless --write is given, but write toggles cover only the Voice and Router APIs, so no key is limited to one product. Browsers use short-lived tokens minted server side, via the bearer_ WebSocket subprotocol, not the URL (25 of 30). The Terms (11 June 2025) say Inworld won't train generally available models on customers' non-public Materials, except feedback and flagged content, while the Privacy Notice (18 January 2026) lists training AI models among its uses, per the inworld-tts check of 4 November (12 of 20). Zero data retention keeps STT audio and transcripts in memory and out of logs, included on Developer ($300 a month) and above per the docs, while the STT page says Enterprise or a Growth add-on. Async results and audio go after 7 days, and no default period is given for logs (8 of 15). Usage is attributed per key and a Performance page shows errors and throttling (8 of 15). SOC 2 Type II and HIPAA claimed and a vulnerability report form, with no security.txt or bug bounty, per the 4 November reading (10 of 20). Total 63.

Cartesia Ink 73

Hosted reading. The status page at status.cartesia.ai (incident.io) lists Speech to Text as its own component in four regions (20). Its RSS feed, re-read on 1 November, now names each incident's components. In the 90 days from 3 August two incidents touch speech-to-text, both partial and read as minor, as this run reads one region or some requests. On 2 September some clients in the US regions saw connection errors that cleared on retry (Text to Speech and Speech to Text, US), and on 7 October customers in the US regions saw higher latency for some API requests, from 12:29 to about 18:23 (partial outage, Text to Speech, Speech to Text and Voice Cloning, US). The 3 September throttling named only Text to Speech in APAC, the 8 October errors only the Playground and Voice Agents, and the 15 October Playground outage says API services were unaffected. The 1 August API-wide incident has left the window. Minor only (20). Concurrency limits are published per plan, 8, 12, 20 and 60 concurrent STT requests, with a 3-minute idle timeout on sockets (15). Exceeding the limit returns 429 with the concurrency_limited code, and the SDKs retry 429 and 5xx twice with backoff on HTTP calls. No Retry-After header, backoff guidance or reconnection advice for a dropped socket was found (8 of 15). No SLA was found for any plan (0). ink-2 is marked Stable on the model page re-read on 1 November, with ink-preview as the preview line (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.

Inworld STT 60

Hosted reading of the checklist. status.inworld.ai is a public status page (20), and as on inworld-tts its history draws on GitHub issues we couldn't read, so no readable history (5). Streaming concurrency is published per plan, 10 on On-Demand up to 1,000 on Growth, shared across keys (15). 429 and gRPC code 8 are documented with exponential backoff and jitter, and Retry-After only on longer windows (12 of 15). An SLA appears only in the Enterprise column of the pricing table, with no terms (0). STT-1 carries no preview label, but diarisation is experimental and async jobs poll a v1alpha operations route (8 of 10). 20 + 5 + 15 + 12 + 0 + 8 = 60.

Cartesia Ink 68

The service is closed and the SDKs are Apache-2.0. The Terms of Service cover the website, its subdomains and APIs, were last revised on 14 June 2024, describe a platform for synthesised sound and never mention transcription (12 of 30). The terms and privacy policy agree that content may be used for training with an opt-out. The DPA says Cartesia will not retain or use customer personal data beyond performing the services, which sits uneasily with the training licence. No retention period is given outside zero data retention, and the privacy policy says the services are designed for users in the United States only while regional endpoints are sold in four other regions (12 of 30). A deprecations page with dated sunsets and a stated promise to preserve fields for a pinned Cartesia-Version (15 of 20). The DPA promises 30 days' notice of sub-processor changes to subscribers and points to a list in the trust centre, which we could not read. Regional deployments are named for Enterprise only (10 of 20).

Inworld STT 60

Closed service with clear terms naming Theai, Inc. dba Inworld AI (15). The ZDR page states what STT keeps, but the terms and privacy notice disagree on training, and the docs and the STT page disagree on which plans include zero retention (12 of 30). No dated STT deprecation or change notices are public (8 of 20). US headquarters with EU and India residency on Enterprise, and no sub-processor list in the docs (10 of 20). Total 45.