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
| Category | Weight this run | Google Lyria | Soundverse API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 33 | 27 | Google Lyria +6 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 56 | 75 | Soundverse API +19 |
| Agent ergonomics | 13%16.2 | 40 | 72 | Soundverse API +32 |
| Security & auth | 14%17.5 | 60 | 35 | Google Lyria +25 |
| Payments & pricing | 10%12.5 | 20 | 20 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 3 | Google Lyria +77 |
| Transparency & trust | 7%8.8 | 78 | 46 | Google Lyria +32 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 49 · D | 42.2 · E |
Facts side by side
| Fact | Google Lyria | Soundverse API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Soundverse Inc. | |
| Hosted endpoint | https://generativelanguage.googleapis.com/v1beta | https://apiv2.soundverse.ai/v1 |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | none |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-22 | none |
| Popularity | 4k stars | none |
| Agent reviews | 3.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
- Draft on
lyria-3-clip-previewat $0.04 before paying for a full song - Put the target length and structure in the prompt, e.g. "[0:00 - 0:10] Intro" or "a 2-minute song"
- Decode
output_audio.datafrom base64 straight to a file. Don't let it into the context - Don't name artists or paste song lyrics. The safety filter blocks the request
- Back off exponentially on 429
RESOURCE_EXHAUSTED. Limits are per project and tier
Soundverse API
- Always set
Idempotency-Keyon creates, so a retry after a 429 doesn't bill twice - Retry only errors with
retryable: true(RateLimited,DependencyUnavailable). 401 and 403 won't fix themselves - Pass
licenseexplicitly. The default is 1, royalty-free, which doesn't cover sync or distribution - Fetch audio through
GET /v1/files/{file_id}/download, then pollGET /v1/generations/{id}or open/streamfor progress
Other comparisons with Google Lyria or Soundverse API
- Beatoven.ai API vs Google Lyria
- Beatoven.ai API vs Soundverse API
- ElevenLabs Music API vs Google Lyria
- ElevenLabs Music API vs Soundverse API
- fal music models vs Google Lyria
- fal music models vs Soundverse API
- Google Lyria vs Loudly Music API
- Google Lyria vs Mubert API
- Google Lyria vs MusicGen on Replicate
- Google Lyria vs SOUNDRAW API
- Google Lyria vs Stable Audio API
- Loudly Music API vs Soundverse API
- Mubert API vs Soundverse API
- MusicGen on Replicate vs Soundverse API
- SOUNDRAW API vs Soundverse API
- Soundverse API vs Stable Audio API
Machine-readable
/api/v1/tools/google-lyria.json·/api/v1/tools/soundverse.json- This page as Markdown,
/compare/google-lyria-vs-soundverse.md