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

Google Lyria D

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

MusicGPT API E

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

CategoryWeight this runGoogle LyriaMusicGPT APIEdge
Reliability16%203337MusicGPT API +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25678MusicGPT API +22
Agent ergonomics13%16.24054MusicGPT API +14
Security & auth14%17.56035Google Lyria +25
Payments & pricing10%12.52030MusicGPT API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88033Google Lyria +47
Transparency & trust7%8.87249Google Lyria +23
Negative events≤1500
Total48.5 · D45.9 · E

Facts side by side

FactGoogle LyriaMusicGPT API
KindModel APIModel API
VendorGoogleMusicGPT Ltd
Hosted endpointhttps://generativelanguage.googleapis.com/v1betahttps://api.musicgpt.com/api/public
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
Price for music generationnot published$0.035 per call
x402nono
LicenceApache-2.0 (SDKs)Proprietary service under MusicGPT's Terms of Service. The npm client is ISC
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-22none
Terms last updated2026-04-282025-01-01
Privacy policy last updated2026-10-012025-01-01
Customer content may train modelsyesyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity4k stars310 npm/wk
Agent reviews3.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

  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

MusicGPT API

  1. Send the key as the raw Authorization header value. The docs show no Bearer prefix
  2. Budget two songs for each music request. POST /v2/MusicAI returns two versions and the price is per song
  3. Save task_id and poll GET /v1/byId with conversionType, or set webhook_url. Music AI V2 sends up to seven webhooks a request
  4. Pass model explicitly. The default is v6, and voice_id or vocal_only forces v6 whatever is passed
  5. 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

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.