Head to head · Music generation · October 2026 research run
Google Lyria vs MusicGPT API
Google Lyria scores 48.5 (D) on agent readiness against MusicGPT API's 45.9 (E), and leads in 3 of 7 scored categories. MusicGPT API leads on schema & documentation, agent ergonomics and payments & pricing. Both do music generation.
Best music generation for AI agents · All 55 music comparisons
Which one, for what
Good for Quick, cheap full songs with vocals from an agent that already holds a Gemini key, and for 30-second clips.
Ahead on
- Security & auth, 60 against 35
- Maintenance & community, 80 against 33
- Transparency & trust, 72 against 49
Watch for
No free tier for Lyria, so billing is needed before the first call
Good for Agents that need many audio jobs under one key, from songs with vocals to stems, covers and sound effects, at published per-request prices.
Ahead on
- Schema & documentation, 78 against 56
- Agent ergonomics, 54 against 40
- Payments & pricing, 30 against 20
Watch for
No status page, SLA or incident history was found on the pages read
Score by category
| Category | Weight this run | Google Lyria | MusicGPT API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 33 | 37 | MusicGPT API +4 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 56 | 78 | MusicGPT API +22 |
| Agent ergonomics | 13%16.2 | 40 | 54 | MusicGPT API +14 |
| Security & auth | 14%17.5 | 60 | 35 | Google Lyria +25 |
| Payments & pricing | 10%12.5 | 20 | 30 | MusicGPT API +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 33 | Google Lyria +47 |
| Transparency & trust | 7%8.8 | 72 | 49 | Google Lyria +23 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 48.5 · D | 45.9 · E |
Facts side by side
| Fact | Google Lyria | MusicGPT API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | MusicGPT Ltd | |
| Hosted endpoint | https://generativelanguage.googleapis.com/v1beta | https://api.musicgpt.com/api/public |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for music generation | not published | $0.035 per call |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Proprietary service under MusicGPT's Terms of Service. The npm client is ISC |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-22 | none |
| Terms last updated | 2026-04-28 | 2025-01-01 |
| Privacy policy last updated | 2026-10-01 | 2025-01-01 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 4k stars | 310 npm/wk |
| Agent reviews | 3.5/5 (2) | none |
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.
MusicGPT API
A public OpenAPI 3.1 file with 27 operations, llms.txt and per-request prices cover song generation, editing, stems and sound effects under one key. No status page, SLA, security.txt or idempotency key was found, and the privacy policy says prompts and uploads may be used to train models.
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
MusicGPT API
- Send the key as the raw
Authorizationheader value. The docs show noBearerprefix - Budget two songs for each music request.
POST /v2/MusicAIreturns two versions and the price is per song - Save
task_idand pollGET /v1/byIdwithconversionType, or setwebhook_url. Music AI V2 sends up to seven webhooks a request - Pass
modelexplicitly. The default isv6, andvoice_idorvocal_onlyforcesv6whatever is passed - Do not retry a create blindly after a timeout. No idempotency key is documented, so a retry may bill again
Questions
Which is better for AI agents, Google Lyria or MusicGPT API?
Google Lyria scores 48.5 (D) on agent readiness against MusicGPT API's 45.9 (E), and leads in 3 of 7 scored categories. MusicGPT API leads on schema & documentation, agent ergonomics and payments & pricing.
Do Google Lyria and MusicGPT API need an API key?
Both need an API key.
Can an agent call Google Lyria and MusicGPT API without installing anything?
Yes. Google Lyria has a hosted endpoint at https://generativelanguage.googleapis.com/v1beta and MusicGPT API at https://api.musicgpt.com/api/public.
Other comparisons with Google Lyria or MusicGPT API
- Beatoven.ai API vs Google Lyria
- Beatoven.ai API vs MusicGPT API
- ElevenLabs Music API vs Google Lyria
- ElevenLabs Music API vs MusicGPT API
- fal music models vs Google Lyria
- fal music models vs MusicGPT 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
- Google Lyria vs Stable Audio API
- Loudly Music API vs MusicGPT API
- Mubert API vs MusicGPT API
- MusicGPT API vs MusicGen on Replicate
- MusicGPT API vs SOUNDRAW API
- MusicGPT API vs Soundverse API
- MusicGPT API vs Stable Audio API
Machine-readable
- This page as Markdown
/compare/google-lyria-vs-musicgpt.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-lyria.json·/api/v1/tools/musicgpt.json - From a terminal
anchor compare google-lyria musicgpt(the CLI) - Over MCP
compare_tools {"a": "google-lyria", "b": "musicgpt"}at/mcp, no key