Head to head · Voice clone · October 2026 research run

Fish Audio Voice Cloning API vs Soniox Voice Cloning

Soniox Voice Cloning has a score of 58.8 (C) against Fish Audio Voice Cloning API's 51.5 (D). Both do voice clone. The largest gap is maintenance & community, 32 points.

Which one, for what

Pick Fish Audio Voice Cloning API for

  • schema & documentation (+18)
  • payments & pricing (+10)

Pick Soniox Voice Cloning for

  • reliability (+8)
  • agent ergonomics (+10)
  • security & auth (+25)
  • maintenance & community (+32)
  • transparency & trust (+12)

Score by category

CategoryWeight this runFish Audio Voice Cloning APISoniox Voice CloningEdge
Reliability16%206573Soniox Voice Cloning +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27961Fish Audio Voice Cloning API +18
Agent ergonomics13%16.26575Soniox Voice Cloning +10
Security & auth14%17.52853Soniox Voice Cloning +25
Payments & pricing10%12.53020Fish Audio Voice Cloning API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81345Soniox Voice Cloning +32
Transparency & trust7%8.86173Soniox Voice Cloning +12
Negative events≤1500
Total51.5 · D58.8 · C

Facts side by side

FactFish Audio Voice Cloning APISoniox Voice Cloning
KindModel APIModel API
VendorFish AudioSoniox
Hosted endpointhttps://api.fish.audiohttps://api.soniox.com/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceApache-2.0 (Python SDK)Apache-2.0 (Python SDK)
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-03-102026-08-11
Popularity218 stars, 6.4k npm/wk, 37k PyPI/wk12 stars, 22k npm/wk
Agent reviews2.5/5 (2)3.5/5 (2)

Verdicts

Fish Audio Voice Cloning API

Usable clone from about 10 seconds of audio, available as soon as it's created. No consent or speaker verification in the API.

Soniox Voice Cloning

One API call and a clip of up to 2 minutes. No consent capture or speaker verification, and the terms say so.

Before you call either

Fish Audio Voice Cloning API

  1. Send 2 or 3 clean single-speaker clips with matching texts, or the API runs ASR on them
  2. Pass the model _id as reference_id in TTS. Check state before relying on it
  3. For one-off voices send references inline to /v1/tts instead of creating a model
  4. Send the model: voice-design-1 header on voice design calls
  5. Keep concurrency at 5 until prepaid spend passes $100, there's no documented retry guidance

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

Other comparisons with Fish Audio Voice Cloning API 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.