Inworld Instant Voice Cloning vs Resemble AI Voice Cloning API

Inworld Instant Voice Cloning 40

No x402, MPP or L402 (0). The pricing page, unread on 9 October and read on 6 November, publishes per-character rates for speech from a clone, $25 per million characters on TTS-2 and $15 on TTS-2 Flash on the free plan, and no charge for creating a clone (20, was 10). The On-Demand plan is free with 100 custom voices and instant cloning, and no card is asked for (20). inworld login opens a browser and signup is a human flow. The CLI mints keys only after that (0). 0+20+20+0 = 40.

Resemble AI Voice Cloning API 0

No x402, MPP or L402 (0). The per-second speech and per-slot prices were read on 30 September from app.resemble.ai/billing/api/v1/plans, a billing data endpoint this run doesn't read, so that reading is struck, and the pricing pages can't be re-read under the terms, so no per-unit price for the API stands today (0). The changelog's $2 for later clones is the Flex web app's, not the API's. No API cloning below Business per the 2 October check, and the free first clone in the Flex web app captures a card for later clones (0). Signup is a human browser flow (0).

Inworld Instant Voice Cloning 68

Read as a model, on the lines inworld-tts and cartesia-voice-cloning use (recency 30, dated releases 10, deprecation notice 10, support 15, SDKs 15, health 10). The 9 October draft used the tool lines and gave 75. @inworld/cli 1.5.0, whose MCP server carries clone_voice, on 29 October 2026, after 1.4.0 (13 October), 1.4.1 (23 October), 1.4.2 and 1.4.3 (25 October) (30). Dated TTS release notes on 9 August and 11 September 2026, and none for the 28 October model update or for the Voice API (10). inworld-tts-1 was discontinued on 15 June 2026 with requests routed to newer models, and clones made before 15 August keep a 15-second prompt, with no notice period stated (5 of 10). A public changelog, a Discord server and support@inworld.ai, with no evidence read of how they answer (8 of 15). @inworld/tts 1.1.1 dates from 6 May 2026 (10 of 15). The CLI is current, but the repositories named in its npm metadata aren't public (5 of 10). 30+10+5+8+10+5 = 68.

Resemble AI Voice Cloning API 30

Newest changelog entry 2026-06-30 per the 2 October check, not re-read on 4 November (terms), 127 days old (10 of 30). No dated entries in the last 90 days that we could read (0). Public changelog, no answering support channel confirmed (5 of 15). The Node SDK clone on 4 November still ends at 754a91e (6 April 2026, 3.5.3, zero-retention mode); Python 1.9.0 of 6 April per PyPI on 2 October, not re-read. Neither has a release since the June model changes (12 of 15). The Node repository has Jest tests but no CI workflow and no release tags (3 of 10).

Inworld Instant Voice Cloning 64

No OpenAPI file is linked from the docs or llms.txt, re-read on 6 November. The MCP server has typed inputs on all 40 tools, which earns part of the line (10 of 25). llms.txt, llms-full.txt and Markdown twins (10). The guides say when to use instant cloning, Professional Voice Cloning or Voice Design, and the reference warns which fields are ignored (15 of 20). Required fields and base64 audio are typed, and a new languageCode string is validated against the catalogue with INVALID_ARGUMENT, while size and length limits sit in prose and the MCP tool still states different ones (10 of 15). Examples in curl, Python, JavaScript and the CLI, with one error response shown and no error list for the Voice API (9 of 15). A /v1/ path and dated TTS release notes, newest 11 September, with no changelog for the Voice API itself (10 of 15). 10+10+15+10+9+10 = 64.

Resemble AI Voice Cloning API 81

Public OpenAPI 3.1 at docs.resemble.ai/openapi.json (25). llms.txt (10). The clone overview separates rapid and professional clones and says how much audio each needs (12 of 20). Typed create fields, including dataset_url, callback_uri and language, and page_size bounded to 10 to 1,000 (12 of 15). Examples, plus dataset quality scores (STOI, PESQ, SI-SDR) for bad recordings. The spec documents only 200 responses on the voice, build and delete operations, and the errors page gives one generic shape, success: false with a message (7 of 15). Versioned /api/v2 paths and a dated public changelog (15). All per the 2 October check, not re-read on 4 November (Resemble's terms bar automated means).

Inworld Instant Voice Cloning 63

Closed service with clear terms naming Theai, Inc. dba Inworld AI, read on 6 November (unread on 9 October because of the Content-Signal line), and MIT client packages on npm (15 of 30, was 8). The Zero Data Retention page is specific that cloning samples are retained to build the voice, but gives no period, and the Terms' no-training clause and the Privacy Notice's training use sit side by side without a reconciling sentence, as on inworld-tts (14 of 30). Dated notices in the docs, inworld-tts-1 discontinued on 15 June 2026 and the 30-second clone limit from 15 August, with release stages defined and no written notice period (12 of 20). US by default with isolated EU and India regions on Enterprise. No sub-processor list was found in the docs (10 of 20). 15+14+12+10 = 51.

Resemble AI Voice Cloning API 75

Closed service with clear terms (15 of 30). The privacy policy of 14 August 2026 states no training on customer voice data, retention while the account is active plus 30 days, no retention of synthesis text or audio, and points to a DPA and a named subprocessor list. That agrees with the terms, which have Resemble destroy voice models on request after termination (25 of 30). The changelog's 29 June 2026 entry says Resemble 'began deprecating all older voice models', with no notice period. The model versions page now lists seven end-of-life TTS models, Chatterbox and Chatterbox-Turbo among them, and says voices still on them can no longer generate audio until upgraded to Resemble Ultra, but gives no dates or notice policy (10 of 20). Subprocessors named at trust.resemble.ai/subprocessors, and hosting stated as the United States on Google Cloud us-east4, Render in Oregon and Cerebrium (20 of 20). Privacy, subprocessor and model-version pages per the 2 October check, not re-read on 4 November (Resemble's terms bar automated means); the terms of 14 August 2026 re-read.

Inworld Instant Voice Cloning 75

Graded on the REST API, the surface an agent would call. Status page at status.inworld.ai, drawn from GitHub issues, with five components and none for cloning (20). Read through the GitHub API on 6 November, the 90 days from 8 August hold two incidents, 29 minutes of elevated TTS latency on 25 August and 26 minutes of elevated TTS 2.1 errors from a network fault at one GPU site on 28 October, both minor (20). Cloning limits are published per plan, 2 to 20 requests a minute (15). A 429 is documented with exponential backoff and jitter code, and since the 9 October check the rate-limits page says limits over a minute can carry Retry-After. No idempotency key or safe-retry guidance for clone creation (10 of 15, was 9). The pricing page, now read, names an SLA on Enterprise only with no terms or figure, as on inworld-tts (0). Instant cloning carries no Preview or Beta mark (10). 20+20+15+10+0+10 = 75.

Resemble AI Voice Cloning API 65

Status page at status.resemble.ai (Checkly) with component history (20). The current components cover the web app, Resemble Ultra TTS and the safety APIs. The history shows a 'Chatterbox Turbo Rapid Voice Clones' component in July that's no longer listed. Since early July the voice surfaces had only short incidents, several of 1 to 5 minutes on rapid voice clones from 6 to 9 July and 1 minute on Ultra TTS on 22 September. The Identities API, a separate product, has had an incident open since 9 September, and Detect had a 50-minute incident on 27 August. Minor incidents only on the voice surfaces (20). 40 requests a second per API token on the rate-limits page, 10 a minute on audio enhancement (15). The rate-limits and error pages say nothing about 429, Retry-After or backoff (0). No SLA found (0). Rapid and professional clones are generally available (10). All per the 2 October check, not re-read on 4 November (Resemble's terms bar automated means). The status history was read to 2 October; the rest of the window from 6 August is unread, so the incident line keeps its recorded 20.