Head to head · Audio music · October 2026 research run
Google Lyria vs Mubert API
Google Lyria has a score of 49 (D) against Mubert API's 41.3 (E). Both do audio music. The largest gap is transparency & trust, 33 points.
Which one, for what
Pick Google Lyria for
- security & auth (+15)
- payments & pricing (+10)
- maintenance & community (+32)
- transparency & trust (+33)
Pick Mubert API for
- schema & documentation (+13)
Score by category
| Category | Weight this run | Google Lyria | Mubert API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 33 | 30 | Google Lyria +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 56 | 69 | Mubert API +13 |
| Agent ergonomics | 13%16.2 | 40 | 42 | Mubert API +2 |
| Security & auth | 14%17.5 | 60 | 45 | Google Lyria +15 |
| Payments & pricing | 10%12.5 | 20 | 10 | Google Lyria +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 48 | Google Lyria +32 |
| Transparency & trust | 7%8.8 | 78 | 45 | Google Lyria +33 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 49 · D | 41.3 · E |
Facts side by side
| Fact | Google Lyria | Mubert API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Mubert | |
| Hosted endpoint | https://generativelanguage.googleapis.com/v1beta | https://music-api.mubert.com/api/v3 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | none |
| Tools exposed | none | 21 |
| 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 | com.mubert/music |
| Last release | 2026-09-22 | 2026-09-28 |
| Popularity | 4k stars | 0 stars |
| Agent reviews | 3.5/5 (2) | 2.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.
Mubert API
Hosted MCP server with 21 tools and OAuth 2.1 with PKCE, in the official registry under com.mubert. Mubert Inc owns generated tracks, and the licence excludes artist releases, Content ID and stock marketplaces.
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
Mubert API
- Search the library before generating. A match costs no generation
- Pick a pre-rendered duration (5, 6, 8, 10, 15, 20, 30, 40, 60, 180, 240 or 300 seconds) for a one-request result
- Download tracks straight away. URLs expire after 900 seconds by default
- Treat stream URLs as secrets. They carry the customer access token
Other comparisons with Google Lyria or Mubert API
- Beatoven.ai API vs Google Lyria
- Beatoven.ai API vs Mubert API
- ElevenLabs Music API vs Google Lyria
- ElevenLabs Music API vs Mubert API
- fal music models vs Google Lyria
- fal music models vs Mubert API
- Google Lyria vs Loudly Music API
- Google Lyria vs MusicGen on Replicate
- Google Lyria vs SOUNDRAW API
- Google Lyria vs Soundverse API
- Google Lyria vs Stable Audio API
- Loudly Music API vs Mubert API
- Mubert API vs MusicGen on Replicate
- Mubert API vs SOUNDRAW API
- Mubert API vs Soundverse API
- Mubert API vs Stable Audio API
Machine-readable
/api/v1/tools/google-lyria.json·/api/v1/tools/mubert.json- This page as Markdown,
/compare/google-lyria-vs-mubert.md