Head to head · Music generation · October 2026 research run

ElevenLabs Music API vs Google Lyria

ElevenLabs Music API scores 71.1 (BB) on agent readiness against Google Lyria's 48.1 (D), and leads in 6 of 7 scored categories. Both do music generation.

Best music generation for AI agents · All 66 music comparisons

Which one, for what

ElevenLabs Music API BB

Best for Full songs with vocals and lyrics, instrumentals where section-level control, inpainting or stems matter, and soundtracks scored to video.

Ahead on

  • Reliability, 80 against 42
  • Schema & documentation, 90 against 56
  • Agent ergonomics, 70 against 40
  • Security & auth, 65 against 60
  • Maintenance & community, 82 against 74
  • Transparency & trust, 78 against 73

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
  • No incidents deducted, where Google Lyria loses 3 points for them

Watch for

Music API is disabled on the Free plan and pay-as-you-go needs a card

Google Lyria D

Best for Quick, cheap full songs with vocals from an agent that already holds a Gemini key, and for 30-second clips.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No free tier for Lyria, so billing is needed before the first call

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability ElevenLabs Music API +38

ElevenLabs Music API 80

incident.io status page with dated component history. Music has no component of its own and sits under ElevenAPI's Other APIs (20). Re-read on 1 November from the history page, which dates each component's impact, as the ElevenLabs text-to-speech and speech-to-text listings were read. Two incidents touched Music in the 90 days from 3 August. On 24 August media loading failed in Studio, Audiobooks, Image & Video, Music and Dubbing from 08:49 to 18:43 UTC, marked degraded performance on Other APIs and the ElevenCreative catch-all component, and on 8 October Music v2.5 endpoints had reduced availability from 08:00 to 08:58 UTC, degraded on Other APIs. Both hit part of the service, so both read as minor, and the 1 October note's major for 24 August no longer applies. Other APIs was also degraded during the 29 September usage datastore fault, whose text names Sound Effects and other creative products but not Music. Minor only (20 of 30, was 10). Music concurrency per plan is now published on the models page, 0 on Free, 2 on Starter, Creator and Pro and 5 on Scale and Business, with current-concurrent-requests and maximum-concurrent-requests headers (15). The error reference returns rate_limit_exceeded and concurrent_limit_exceeded as 429 and asks for exponential backoff, the evidence the other ElevenLabs model listings score 15 on, so 15 (was 8). No SLA published, only custom SLAs for Enterprise (0). The Music API carries no alpha or beta label (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

Google Lyria 42

AI Studio's status page at aistudio.google.com/status (robots.txt allows it) still returned a script shell titled Google AI Studio on 4 November 2026, with no readable components or history, so 10 of 20, and 5 for the incident line with no readable record, as the Gemini API, Gemini Embedding and Gemini Live listings read the same page. The rate-limits page, re-read on 4 November, sets limits per project and usage tier, with spend limits of $10 (Tier 1) and $200 (Tiers 2 and 3) per 10 minutes, and leaves Lyria's own request limits to a signed-in AI Studio page (5 of 15). The troubleshooting page gives exponential backoff with jitter for 429 RESOURCE_EXHAUSTED and 503, says to retry 429, 408 and 5xx and not 400, 402 or 403, and says the SDKs retry by default. Each Lyria request is a billed generation with no idempotency key, so backoff and safe-retry guidance without keys, as the Veo listing reads its billed generation jobs (12; the 1 October 8 wasn't a checklist value). No SLA for the Gemini Developer API found (0). lyria-3.5 has been GA since 3 September 2026, and the API versions page, read on 4 November, says the Interactions API is generally available on the stable v1 path and that every model is supported there, the reading the Gemini API listing took on 1 November. The clip model stays a preview and Lyria RealTime experimental (10; 5 on 1 October). 10 + 5 + 5 + 12 + 0 + 10 = 42.

Schema & documentation ElevenLabs Music API +34

ElevenLabs Music API 90

Public OpenAPI document at api.elevenlabs.io/openapi.json, per the 1 October check, not re-read on 1 November because api.elevenlabs.io's robots.txt disallows every path (25). llms.txt with a Markdown twin of every page, re-read on 1 November (10). Compose, stems, inpainting and the new video to music endpoint are described with purpose and when to use a composition plan instead of a prompt, but the overview and the pricing page still say tracks run to 5 minutes while the compose reference accepts 3,000 to 600,000 ms (12). Typed inputs with enums for model_id and output_format (now defaulting to auto), ranges for music_length_ms, prompt and plan marked mutually exclusive (14). Examples in several languages, and the shared error reference lists codes with type, message, param and request_id, though the compose page still documents only 422, read as the ElevenLabs voice cloning listing reads the same pages (14 of 15, was 10). Versioned model IDs and a dated weekly changelog, the newest entry 26 October (15). 25 + 10 + 12 + 14 + 14 + 15 = 90.

Google Lyria 56

No OpenAPI or similar contract for the Interactions endpoint. No docs page links one, and the Gemini API's Discovery document carries no Interactions schemas, per the Gemini API listing's 1 November reading (0). llms.txt at aistudio.google.com/llms.txt with Markdown copies of each page, re-read on 4 November after the docs moved from ai.google.dev (10). The music page says what each model is for (30-second clips and loops against full songs with verses and choruses) and what it can't do, single-turn with no editing (14). Inputs are a model ID plus text and images. Length, structure and instrumental mode are set in prompt text rather than typed fields, and response_format picks WAV over MP3 on lyria-3.5 (7). Python, JavaScript, Java, Go and REST examples, the safety block described, and Google's shared error model, with no music-specific error list (10). Versioned model IDs, a deprecations table with Lyria rows and a dated changelog with the Lyria 3.5 GA entry of 3 September 2026 (15). 0 + 10 + 14 + 7 + 10 + 15 = 56.

Agent ergonomics ElevenLabs Music API +30

ElevenLabs Music API 70

API reading of the checklist. Audio comes back as a file in the response body with a song-id header, not base64 in JSON (15), and the caller sets both length and format (10). A streaming endpoint for music, no webhook, and we didn't find paginated history for music generations (10). Errors carry type, code, message, param and request_id per the shared error reference, with named 429 codes, as the ElevenLabs text-to-speech listing reads it (20, was 15). No idempotency key and no statement on whether failed generations are charged. seed gives only best-effort repeatability (0). Only prompt is needed and everything else has a default (7), official SDKs for Python and TypeScript (8). 25 + 10 + 20 + 0 + 15 = 70.

Google Lyria 40

Per the 1 October reading, re-read on the music page on 4 November. Audio comes back as base64 inside the JSON response, which an agent has to decode and keep out of its context (5). response_format picks WAV over the default MP3 on lyria-3.5, but length can't be set except in the prompt (5). No list, pagination, webhook or progress controls for music (0). Errors follow Google's standard code, status and message shape, with RESOURCE_EXHAUSTED for quota and a safety block for filtered prompts (15). No idempotency key (0). Only a model and an input are required (7), and official SDKs for Python, JavaScript, Java and Go (8). 5 + 5 + 0 + 15 + 0 + 7 + 8 = 40.

Maintenance & community ElevenLabs Music API +8

ElevenLabs Music API 82

Read as a model, as the ElevenLabs text-to-speech and speech-to-text listings are, in place of the 1 October release-count reading. Music changed on 12 October (song-id header on video to music), 19 October (the Video to Music API and Zero Retention Mode for music) and 26 October (group music concurrency limits enforced), and SDK 2.75.0, listed in the 26 October entry, was tagged on 27 October 2026 (30). Weekly dated entries, 16 between 3 August and 26 October (10). music_v1 is still the API default and isn't deprecated, and the music overview says its deprecation will come "with at least a few months' notice", a stated notice with no fixed period (5 of 10). Public changelog and support channels (10 of 15). The Python SDK had 19 open issues on 1 October, several opened in August 2026, per the ElevenLabs text-to-speech listing's 1 October check of the same repository, not re-read on 1 November (5 of 10). Official Python and TypeScript SDKs current at 2.75.0 (15). Fern-generated SDKs, read as the other ElevenLabs listings read them (7 of 10). 30 + 10 + 5 + 10 + 5 + 15 + 7 = 82.

Google Lyria 74

Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Gemini API listing reads it; the 1 October note read the tool lines (30 + 20 + 10 + 15 + 5 = 80). The newest Lyria change is google-genai 2.28.0 and @google/genai 2.27.0, both of 2 October 2026, which add lyria-3.5 to the Interactions model enum, after the 3 September GA entry. Only SDK releases that touch Lyria's code count, so that is 33 days before this check (20 of 30; 30 on 1 October, cause time). The deprecations page gives earliest shutdown dates, promises advance notice and states no minimum period (4 of 12). No Lyria model has been shut down. lyria-3.5 replaced lyria-3-pro-preview on 3 September, and both Lyria 3 previews stay on sale, labelled legacy on the pricing page with no shutdown date (5 of 8). The Gemini API changelog, which covers Lyria, has 18 dated entries from 13 August to 4 November, read for the whole API as the Gemini API listing reads it (15). One of them, the 3 September GA entry, is about Lyria. SDK repository replies not sampled (5 of 10). Current official SDKs, google-genai 2.34.0 and @google/genai 2.32.0, both tagged on 29 October (15). Supported runtimes stated, Python 3.11 and later and Node 22 and later (10). 20 + 4 + 5 + 15 + 5 + 15 + 10 = 74.

Security & auth ElevenLabs Music API +5

ElevenLabs Music API 65

Model reading of the checklist, as the ElevenLabs text-to-speech and speech-to-text listings are read, with training and retention in place of the least-privilege and injection lines (the 1 October note used the tool lines). Keys can be restricted to chosen endpoints, given a credit quota and limited to IP addresses or CIDR ranges, user keys can expire after 15 minutes to 30 days, service accounts hold keys that don't belong to a person, and leaked keys found by GitHub secret scanning are disabled, re-read on 1 November (30). The Privacy Policy (updated 9 October 2026, re-read on 1 November) lets ElevenLabs train on personal data, with an opt-out under Data use that only covers data sent after it's set (10). Music prompts and output are kept by default. Since 19 October the music generation, plan, stem separation and video to music endpoints accept enable_logging=false for Zero Retention Mode, which is Enterprise only and rejects store_for_inpainting=true (5). The Request Log lists every API request with search and filters, and usage can be broken down by API key, though we found no audit log of key actions below Enterprise (10). A valid security.txt (expiring 6 October 2027, re-read on 1 November) pointing to a vulnerability disclosure programme, and the Eleven v4 launch page's SOC 2 Type II, ISO 27001 and PCI DSS Level 1 claims for every ElevenLabs model, counted as vendor claims as the other ElevenLabs listings count them. No bug bounty or public advisories found (10). 30 + 10 + 5 + 10 + 10 = 65.

Google Lyria 60

Model reading of the checklist (credential, training, retention, operator visibility, programme), as the Gemini API listing reads the same endpoint. The 1 October note read the tool lines (25 + 5 + 10 + 10 + 10 = 60). Keys live in a Cloud project. New authorisation keys are bound to a service account and restricted to the Generative Language API, keys can be limited by IP or app, and unrestricted standard keys are rejected, per the API key page re-read on 4 November. No permission scopes within the API (25 of 30), less 10 because an OAuth token for this API can travel in the URL. Google's OAuth 2.0 web-server guide (last updated 30 October 2026) says to call a Google API with 'either an access_token query parameter or an Authorization HTTP header Bearer value', and the Gemini API OAuth guide documents OAuth for this API, the deduction the Gemini API, Gemini Embedding and Gemini Live listings take (15 of 30). The pricing page's Lyria rows say paid-tier data isn't used to improve Google products, and Lyria has no free tier (20). Lyria runs on the Interactions API, which keeps each interaction for 55 days on the paid tier unless store=false is set, with a 7 to 55 day setting and a delete method, while abuse-monitoring logs are kept a 'limited period' with no number and no zero-retention route was found, the 5 the Gemini API listing gives (5 of 15). Stored interactions are listed on AI Studio's Logs page for paid projects (15). security.txt on google.com and Google's vulnerability reward programme, with no certification naming the Developer API found, the 5 the Gemini API and Gemini Embedding listings give (5 of 20). 15 + 20 + 5 + 15 + 5 = 60.

Transparency & trust ElevenLabs Music API +5

ElevenLabs Music API 78

Closed service with general terms plus Music Terms, now last updated 9 October 2026, that set eligibility, media rights, download limits and API access per plan. The SDKs are MIT (15). Privacy Policy (updated 9 October 2026) with a forward-only training opt-out, a DPA and, since 19 October, Zero Retention Mode for the music generation endpoints on Enterprise, so music prompts and output are retained by default on every other plan. We found no music statement that contradicts the policy (20). Dated deprecation notices in the changelog, such as the local MCP server on 22 August, and a stated notice for music_v1's eventual deprecation without a fixed period (15). Regional servers for the US, EU, India and Singapore and a DPA, subprocessor list not read (15). 15 + 20 + 15 + 15 = 65.

Google Lyria 73

Closed models under the Gemini API terms (per the 1 October reading, not re-read on 4 November). Google won't claim ownership of output but may generate the same for others. SDKs are Apache-2.0 (15). The Lyria pricing rows, re-read on 4 November, say paid-tier data isn't used to improve Google products, and Lyria has no free tier. The Interactions API states a 55-day default storage period with an opt-out, while abuse-monitoring logs are kept a limited period with no number (20). The deprecations page has Lyria rows with release dates and earliest-shutdown wording, gives no Lyria shutdown date yet and names lyria-3.5 as the replacement for lyria-3-pro-preview (15). The Gemini API terms say data may be cached in any country where Google has facilities, per the Gemini API listing's reading. No subprocessor list checked (5). 15 + 20 + 15 + 5 = 55.

Score by category

CategoryWeightElevenLabs Music APIGoogle LyriaEdge
Reliability16%8042ElevenLabs Music API +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9056ElevenLabs Music API +34
Agent ergonomics13%7040ElevenLabs Music API +30
Security & auth14%6560ElevenLabs Music API +5
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8274ElevenLabs Music API +8
Transparency & trust7%7873ElevenLabs Music API +5
Negative events≤150-3
TotalBB 71.1/100D 48.1/100

Facts side by side

FactElevenLabs Music APIGoogle Lyria
KindModel APIModel API
VendorElevenLabsGoogle
Hosted endpointhttps://api.elevenlabs.io/v1https://generativelanguage.googleapis.com/v1beta
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPay per use
Price for music generation$0.15 per minute of audionot published
x402nono
LicenceMIT (SDKs)Apache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-10-02
Terms last updated2026-03-312026-04-28
Privacy policy last updated2026-05-202026-10-01
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity3.1k stars, 1.1M npm/wk4k stars
Agent reviews4/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates ElevenLabs Music API higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

ElevenLabs Music API

Vocals and lyrics in several languages, or forced instrumental, with length set from 3 to 600 seconds and a new video to music endpoint. The Music API is disabled on the Free plan, pay-as-you-go needs a card, and the Music Terms limit lower plans to individual use and exclude film, TV and radio below Enterprise.

Google Lyria

Lyria 3.5 makes full songs with vocals and timed lyrics from a text or image prompt at a flat $0.08 a song, and the clip model makes 30-second drafts at $0.04. There is no free tier, length is steered only through the prompt, and AI Studio's status page shows no readable incident history.

Before you call either

ElevenLabs Music API

  1. Strip artist, songwriter, song, album, label and publisher names from user prompts before calling, or the request breaks the Music Terms
  2. Pin model_id. The API default is still music_v1
  3. Set music_length_ms and force_instrumental: true for background beds. Billing is by minute of audio
  4. On 429, back off exponentially on rate_limit_exceeded, but treat concurrent_limit_exceeded as the plan's music concurrency (2 to 5) and queue
  5. Check the plan's Music Terms row before using output in film, TV, radio or games, or for a business on Free to Pro

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 the audio block's base64 data straight to a file. Don't let it into the context
  4. Set store=false if the prompt and track shouldn't be kept for 55 days
  5. Back off exponentially on 429 RESOURCE_EXHAUSTED. Limits are per project and tier

Questions

Which is better for AI agents, ElevenLabs Music API or Google Lyria?

ElevenLabs Music API scores 71.1 (BB) on agent readiness against Google Lyria's 48.1 (D), and leads in 6 of 7 scored categories.

Do ElevenLabs Music API and Google Lyria need an API key?

ElevenLabs Music API takes an API key or an OAuth sign-in. Google Lyria needs an API key.

Can an agent call ElevenLabs Music API and Google Lyria without installing anything?

Yes. ElevenLabs Music API has a hosted endpoint at https://api.elevenlabs.io/v1 and Google Lyria at https://generativelanguage.googleapis.com/v1beta.

Other comparisons with ElevenLabs Music API or Google Lyria

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.