Head to head · Audio music · October 2026 research run
Google Lyria vs Stable Audio API
Stable Audio API has a score of 50.3 (D) against Google Lyria's 49 (D). Both do audio music. The largest gap is maintenance & community, 65 points.
Which one, for what
Pick Google Lyria for
- security & auth (+30)
- maintenance & community (+65)
- transparency & trust (+13)
Pick Stable Audio API for
- reliability (+32)
- schema & documentation (+23)
- agent ergonomics (+20)
Score by category
| Category | Weight this run | Google Lyria | Stable Audio API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 33 | 65 | Stable Audio API +32 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 56 | 79 | Stable Audio API +23 |
| Agent ergonomics | 13%16.2 | 40 | 60 | Stable Audio API +20 |
| Security & auth | 14%17.5 | 60 | 30 | Google Lyria +30 |
| 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 | 15 | Google Lyria +65 |
| Transparency & trust | 7%8.8 | 78 | 65 | Google Lyria +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 49 · D | 50.3 · D |
Facts side by side
| Fact | Google Lyria | Stable Audio API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Stability AI | |
| Hosted endpoint | https://generativelanguage.googleapis.com/v1beta | https://api.stability.ai/v2beta |
| 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 | no |
| MCP registry | not listed | not listed |
| Last release | 2026-09-22 | none |
| Popularity | 4k stars | none |
| Agent reviews | 3.5/5 (2) | 3.5/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.
Stable Audio API
Pay-as-you-go credits, $0.26 a 3.0 generation and $0.20 on 2.5, failures free. Stable Audio 3.0 is async only, with polling and no webhook, and inpaint stays on 2 and 2.5.
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
Stable Audio API
- On
stable-audio/*routes, expect HTTP 202 and anid, then pollGET /v2beta/audio/results/{id}until 200 - Send
accept: audio/*for raw bytes, not base64 JSON - Set
duration. It defaults to 190 seconds on 3.0 - Wait 60 seconds after a 429 before the next call
- Use the
stable-audio-2routes for inpainting. 3.0 has no inpaint route
Other comparisons with Google Lyria or Stable Audio API
- Beatoven.ai API vs Google Lyria
- Beatoven.ai API vs Stable Audio API
- ElevenLabs Music API vs Google Lyria
- ElevenLabs Music API vs Stable Audio API
- fal music models vs Google Lyria
- fal music models vs Stable Audio 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 Soundverse API
- Loudly Music API vs Stable Audio API
- Mubert API vs Stable Audio API
- MusicGen on Replicate vs Stable Audio API
- SOUNDRAW API vs Stable Audio API
- Soundverse API vs Stable Audio API
Machine-readable
/api/v1/tools/google-lyria.json·/api/v1/tools/stable-audio.json- This page as Markdown,
/compare/google-lyria-vs-stable-audio.md