Head to head · Audio music · October 2026 research run

Google Lyria vs Soundverse API

Google Lyria has a score of 49 (D) against Soundverse API's 42.2 (E). Both do audio music. The largest gap is maintenance & community, 77 points.

Which one, for what

Pick Google Lyria for

  • reliability (+6)
  • security & auth (+25)
  • maintenance & community (+77)
  • transparency & trust (+32)

Pick Soundverse API for

  • schema & documentation (+19)
  • agent ergonomics (+32)

Score by category

CategoryWeight this runGoogle LyriaSoundverse APIEdge
Reliability16%203327Google Lyria +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25675Soundverse API +19
Agent ergonomics13%16.24072Soundverse API +32
Security & auth14%17.56035Google Lyria +25
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8803Google Lyria +77
Transparency & trust7%8.87846Google Lyria +32
Negative events≤1500
Total49 · D42.2 · E

Facts side by side

FactGoogle LyriaSoundverse API
KindModel APIModel API
VendorGoogleSoundverse Inc.
Hosted endpointhttps://generativelanguage.googleapis.com/v1betahttps://apiv2.soundverse.ai/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceApache-2.0 (SDKs)none
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-09-22none
Popularity4k starsnone
Agent reviews3.5/5 (2)4/5 (2)

Verdicts

Google Lyria

$0.08 a full song on lyria-3.5 and $0.04 a 30-second clip, flat. No free tier for Lyria, so billing is needed before the first call.

Soundverse API

Songs with vocals, instrumentals, stems (2, 6 or 12), SFX and remix behind one endpoint. No status page, changelog or security.txt.

Before you call either

Google Lyria

  1. Draft on lyria-3-clip-preview at $0.04 before paying for a full song
  2. Put the target length and structure in the prompt, e.g. "[0:00 - 0:10] Intro" or "a 2-minute song"
  3. Decode output_audio.data from base64 straight to a file. Don't let it into the context
  4. Don't name artists or paste song lyrics. The safety filter blocks the request
  5. Back off exponentially on 429 RESOURCE_EXHAUSTED. Limits are per project and tier

Soundverse API

  1. Always set Idempotency-Key on creates, so a retry after a 429 doesn't bill twice
  2. Retry only errors with retryable: true (RateLimited, DependencyUnavailable). 401 and 403 won't fix themselves
  3. Pass license explicitly. The default is 1, royalty-free, which doesn't cover sync or distribution
  4. Fetch audio through GET /v1/files/{file_id}/download, then poll GET /v1/generations/{id} or open /stream for progress

Other comparisons with Google Lyria or Soundverse API

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.