Head to head · Voice cloning · October 2026 research run

Gradium Voice Cloning and Voice Design vs Soniox Voice Cloning

Soniox Voice Cloning scores 68.7 (B) on agent readiness against Gradium Voice Cloning and Voice Design's 60.8 (C), and leads in 6 of 7 scored categories. Gradium Voice Cloning and Voice Design leads on payments & pricing. Both do voice cloning.

Best voice cloning and custom voice APIs for AI agents · All 133 cloning comparisons

Which one, for what

Gradium Voice Cloning and Voice Design C

Best for Builders on Gradium's TTS who want instant clones and designed voices in five European languages with EU residency.

Ahead on

  • Payments & pricing, 30 against 20

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Soniox Voice Cloning loses 3 points for them

Watch for

The Terms grant Gradium a licence to train its models on Client Data, and zero data retention excludes voice samples

Soniox Voice Cloning B

Best for A quick clone that has to speak many languages, from a vendor with clean data terms.

Ahead on

  • Reliability, 87 against 63
  • Agent ergonomics, 82 against 67
  • Security & auth, 67 against 48
  • Maintenance & community, 75 against 70
  • Transparency & trust, 71 against 63

Watch for

No consent capture or speaker verification, and the terms say so

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Soniox Voice Cloning +24

Gradium Voice Cloning and Voice Design 63

Graded on the hosted voice API with the hosted lines. Atlassian Statuspage at gradium.statuspage.io with five components, one of them Voice Cloning (20). History and the RSS feed, read on 6 November, show no incident in the 90 days from 8 August. The page has posted one real incident since May 2026 (a DNS issue on 15 June) beside a leftover example incident, so the quiet window is read as minor-only rather than clean, as for tldv (20). Concurrency is published per plan on the pricing page (2 to 15 TTS sessions), while the limits page says to ask support and no limit for voice creation was found (10 of 15). No 429, Retry-After or backoff guidance was found; the errors page says to open a new connection after an error, and voice creation takes a timeout_s (3 of 15). No SLA in the Terms or on the pricing page (0). Instant cloning carries no beta label (10). 20+20+10+3+0+10 = 63.

Soniox Voice Cloning 87

Instatus page at status.soniox.com with five components in each of the US, Europe, Japan and India groups plus the Console, and a dated notice history (20). In the 90 days from 6 August the page posted three incidents, failed API key creation in the Console for 1 hour 10 minutes on 24 August, failed new EU real-time STT connections for 9 minutes on 25 August and Japan real-time STT overload for 45 minutes on 8 September, and none for October or November. None touches TTS or voices, so the record is clean for this listing, read as soniox-tts (30; was 20). TTS REST limits published, 100 requests a minute and 3 concurrent requests, and 20 voices per organisation (15). A 429 returns limit_exceeded; the OpenAPI file says to retry a 429 after a delay, retry a 408 and retry a 503 with backoff. No Retry-After and no idempotency key on voice creation, though a repeated create with the same name is refused because names are unique per project. Safe-retry guidance without idempotency keys earns 12, as soniox-tts (12; was 8). No SLA found (0). Voice cloning is part of the GA tts-rt-v2 model (10). 20 + 30 + 15 + 12 + 0 + 10 = 87.

Security & auth Soniox Voice Cloning +19

Gradium Voice Cloning and Voice Design 48

Graded for voice cloning as the other listings in this category, with consent and misuse controls in place of the read-only line and training and retention of voice data in place of the prompt-injection line. API keys per organisation in a header, revocable and able to expire, with no scopes found (20 of 30). No consent or verification field and no watermark. The Terms make the client obtain the consent of anyone whose voice is a sample and bar impersonation without explicit authorisation, and the API FAQ says explicit consent is required (6 of 20). The Terms grant Gradium a licence to use Client Data to improve its services and train its models, with no opt-out found, and zero data retention (paid plans) excludes voice samples, so samples are kept and may be used for training (2 of 15). Organisation roles and a member list, with no per-call audit log found (5 of 15). SOC 2 Type II and ISO 27001:2022 audited by A-LIGN, a trust centre and security@gradium.ai. No security.txt (404) and no bug bounty found (15 of 20). 20+6+2+5+15 = 48.

Soniox Voice Cloning 67

Graded for voice cloning, with consent and misuse controls in place of the read-only line and training and retention of voice data in place of the prompt-injection line, since the API returns audio and IDs rather than third-party text. Project API keys carry permissions per resource, with read and write levels for cloned voices, a missing permission returns 403 permission_denied, and temporary keys serve browser clients (30; was 25). The terms say Soniox doesn't verify the right to clone a voice, and there's no consent step or watermark, per the 1 October check, not re-read on 4 November (0 of 20). Audio is never used to improve models, and a voice's clip stays until you delete the voice (15). Per-request usage logs and every error's request_id, as soniox-tts reads them (10 of 15; was 8). SOC 2 Type 2 and ISO/IEC 27001:2022 stated; the Python SDK's SECURITY.md gives a disclosure route by email, GitHub, a maintainer or Discord; soniox.com/.well-known/security.txt answers 404 and no bug bounty was found, as soniox-tts (12 of 20; was 5). 30 + 0 + 15 + 10 + 12 = 67.

Agent ergonomics Soniox Voice Cloning +15

Gradium Voice Cloning and Voice Design 67

Voice objects are compact metadata (20 of 25). GET /voices/ takes skip and limit (default 100) and since 23 October filters by locale, gender and use_case (20). Validation errors are structured 422 bodies, while synthesis errors arrive as plain-text HTTP 500 with a numeric code to parse (12 of 20). No idempotency key. Saving a design candidate twice answers 409, and the clone call has none (5 of 20). Three required fields with sensible defaults, and one official SDK, in Python (10 of 15). 20+20+12+5+10 = 67.

Soniox Voice Cloning 82

Responses are small voice objects, and the OpenAPI file says the list returns the voices in your project (22 of 25; was 20). The voices list pages with limit (up to 1,000) and a cursor, and a count endpoint returns the total, with no filters on custom voices (15 of 20; was 10). Errors say which to retry and which are terminal, and voice_not_prepared tells you to recompute (20). No idempotency key; voice processing has a per-model status to poll, and a duplicate name is refused (10 of 20). Two required fields and SDKs for Python, Node, the web and React (15). 22 + 15 + 20 + 10 + 15 = 82.

Payments & pricing Gradium Voice Cloning and Voice Design +10

Gradium Voice Cloning and Voice Design 30

No x402, MPP or L402 (0). Plan prices and credits are public, 1 credit a character for speech, with no dollar price per unit, as cartesia-voice-cloning is read. Creating a clone uses no credits in the docs (10). The free plan has 45,000 credits a month, 5 custom voices and Voice Design, and the site says no credit card is required. Commercial use starts on the $12 plan (20). Signup is a browser flow in Gradium Studio (0). 0+10+20+0 = 30.

Soniox Voice Cloning 20

No x402, MPP or L402 (0). Per-unit prices are public, $4 per million input text tokens and $21.50 per million output audio tokens, about $0.70 an hour by Soniox's estimate, with no cloning fee (20). No free tier for new accounts (0). Signup is a human browser flow (0).

Transparency & trust Soniox Voice Cloning +8

Gradium Voice Cloning and Voice Design 63

Closed service with clear terms, version of 19 October 2026, naming Gradium SAS with its Paris registration (15 of 30). The Terms allow training on Client Data, zero data retention excludes voice samples, the privacy policy gives retention criteria without periods, and a DPA is published as an exhibit. The statements agree but give no retention period for samples (15 of 30). Deprecations appear in dated release notes, with no written notice policy (10 of 20). EU and US residency is documented and selectable from the XS plan. Sub-processors sit in the trust centre, not read (12 of 20). 15+15+10+12 = 52.

Soniox Voice Cloning 71

Closed service with clear terms, SDKs open source (15 of 30). Terms and privacy updated 2026-06-29 agree that samples aren't used for training and stay until deleted, with Async data auto-deleted after 30 days, but we found no public DPA or subprocessor list (20 of 30). Deprecation guidance and model aliases on the models page (15 of 20). Data residency documented, with regions in the US, Europe, Japan and India, no subprocessor list found (10 of 20). Per the 1 October check for the terms and privacy policy, not re-read on 4 November; the security page still says audio is never used to improve models and Async data is deleted after 30 days. 15 + 20 + 15 + 10 = 60.

Maintenance & community Soniox Voice Cloning +5

Gradium Voice Cloning and Voice Design 70

Read as a model, on the lines the other hosted cloning listings use (recency 30, dated releases 10, deprecation notice 10, support 15, SDKs 15, health 10). Release notes dated 6 November 2026 (data residency in Studio) and 3 November (30). Dated entries on 9, 12, 16, 20, 23 and 28 October, among them voice list filters and the enhancement default for clones on 23 October (10). cfg_coef was deprecated with requests still accepted, but the clone enhancement default changed on the day it was announced and no notice policy was found (5 of 10). Public release notes, support@gradium.ai and a Discord server, with no evidence read of how they answer (10 of 15). gradium on PyPI at 0.6.4 (4 September 2026), with no SDK in a second language (10 of 15). The SDK repository was not cloned (5 of 10). 30+10+5+10+10+5 = 70.

Soniox Voice Cloning 75

Read as a model, on the lines soniox-tts, deepgram-tts 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 1 October note used the tool lines. Python SDK soniox 2.11.0 on 3 November 2026 adds voice permissions and voice limits to its types, and the JavaScript tag v2026.11.03 ships @soniox/node 2.5.0 the same day (30; was 20). In the 90 days from 6 August, tts-rt-v2 GA with high-fidelity cloning (11 August), the tts-rt-v1 removal (31 August), Python 2.9.0 (11 August, adds the voices client), 2.10.0 (2 October) and 2.11.0 (3 November), and JavaScript tags v2026.08.11, v2026.10.12 and v2026.11.03 (10). tts-rt-v1 was removed 20 days after its deprecation notice, while the deprecation of api_key in WebSocket config messages carries a 15 January 2027 deadline with a migration guide (5 of 10). The models page and a support channel, untested (5 of 15). SDK issues couldn't be read because GitHub's pages answered 403 (3 of 10). SDKs for Python, Node, the web and React (15). soniox-js runs a CI workflow on every push (lint and tests); the Python SDK has tests and a lock file but no workflow in its clone (7 of 10). 30 + 10 + 5 + 5 + 3 + 15 + 7 = 75.

Score by category

CategoryWeight this runGradium Voice Cloning and Voice DesignSoniox Voice CloningEdge
Reliability16%206387Soniox Voice Cloning +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28386Soniox Voice Cloning +3
Agent ergonomics13%16.26782Soniox Voice Cloning +15
Security & auth14%17.54867Soniox Voice Cloning +19
Payments & pricing10%12.53020Gradium Voice Cloning and Voice Design +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87075Soniox Voice Cloning +5
Transparency & trust7%8.86371Soniox Voice Cloning +8
Negative events≤150-3
TotalC 60.8/100B 68.7/100

Facts side by side

FactGradium Voice Cloning and Voice DesignSoniox Voice Cloning
KindModel APIModel API
VendorGradium SASSoniox
Hosted endpointhttps://api.gradium.ai/api/voices/https://api.soniox.com/v1
TransportsHTTP, websocketHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
Price for voice cloningnot published$0.0117 per minute of audio
x402nono
LicenceProprietary service under Gradium's Terms of Service (version of 19 October 2026). The gradium Python SDK is on PyPIApache-2.0 (Python SDK)
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-062026-11-03
Terms last updatedno date given2026-06-29
Privacy policy last updatedno date given2026-06-29
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone12 stars, 22k npm/wk
Agent reviewsnone3.5/5 (2)

How the scores have moved

Verdicts

Gradium Voice Cloning and Voice Design

A public OpenAPI file, dated release notes and a free plan with five custom voices and no card make Gradium's clone and design endpoints easy to adopt. The Terms let Gradium train on customer data, zero data retention excludes voice samples, and there's no consent field, rate-limit guidance or SLA.

Soniox Voice Cloning

One API call and a clip of up to 2 minutes, with an OpenAPI file covering create, list, recompute and delete. No consent capture or speaker verification, and the terms say so. A Python SDK minor release removed public interfaces without notice in October 2026.

Before you call either

Gradium Voice Cloning and Voice Design

  1. Send language on every clone. It's required and must be one of en, fr, de, es or pt and match the recording
  2. Clones are enhanced by default since 23 October 2026. Pass enhance=false to keep the raw voice, then check enhance on GET
  3. Pass a clone as voice_id in TTS, not voice
  4. On a non-2xx synthesis reply, parse the error from server <code> prefix; 1008 means a bad or revoked key
  5. Check the custom-voice allowance first. The free plan holds 5 voices shared by clones and designs

Soniox Voice Cloning

  1. Poll the voice until the target model's status is ready before using it in TTS
  2. On voice_not_prepared call recompute, don't retry the TTS request
  3. Don't retry voice_failed even though it's a 503. Create a new voice from a better clip
  4. Use a key from the project that owns the voice, voices are per project
  5. Keep the clip under 2 minutes and 35 MB, longer fails with voice_audio_too_long
  6. Send the API key with the WebSocket connection, not in the config message, before 15 January 2027

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Gradium Voice Cloning and Voice Design or Soniox Voice Cloning?

Soniox Voice Cloning scores 68.7 (B) on agent readiness against Gradium Voice Cloning and Voice Design's 60.8 (C), and leads in 6 of 7 scored categories. Gradium Voice Cloning and Voice Design leads on payments & pricing.

Do Gradium Voice Cloning and Voice Design and Soniox Voice Cloning need an API key?

Both need an API key.

Can an agent call Gradium Voice Cloning and Voice Design and Soniox Voice Cloning without installing anything?

Yes. Gradium Voice Cloning and Voice Design has a hosted endpoint at https://api.gradium.ai/api/voices/ and Soniox Voice Cloning at https://api.soniox.com/v1.

Other comparisons with Gradium Voice Cloning and Voice Design or Soniox Voice Cloning

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.