Head to head · Music generation · October 2026 research run

fal music models vs Soundverse API

fal music models scores 72.6 (BB) on agent readiness against Soundverse API's 42.4 (E), and leads in 6 of 7 scored categories. Both do music generation. Soundverse API is cheaper for music generation, $0.07 against $0.15 per call.

Best music generation for AI agents · All 66 music comparisons

Which one, for what

fal music models BB

Best for An agent or team that wants to compare or switch music models without a contract per vendor, with a published price per model.

Ahead on

  • Reliability, 77 against 27
  • Schema & documentation, 89 against 75
  • Agent ergonomics, 83 against 72
  • Security & auth, 73 against 25
  • Maintenance & community, 82 against 11
  • Transparency & trust, 64 against 46

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Billing units differ per model (per track, per second, per song, per minute rounded up)

Soundverse API E

Best for Agents that need several music jobs from one vendor (song, stems, SFX, remix, copyright check) and want to buy the exact rights for each file.

Also in its favour

  • Cheaper for music generation, $0.07 against $0.15 per call

Watch for

No status page, changelog or security.txt

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.

Maintenance & community fal music models +71

fal music models 82

The changelog's newest entry is 29 October 2026 (fallback chains), and the catalogue shows Mureka 8 and 9 music endpoints added on 22, 23 and 26 October (30). 11 dated changelog entries from 3 August to 29 October 2026 (20). Public changelog and dashboard support, response times not checked (10). Python client at 1.0.3 (repository tag fal_client_v1.0.3, 18 September 2026; 21 September on PyPI per the 1 October check, not re-read on 1 November), JavaScript client last released as 1.10.1 (tag client-v1.10.1, 4 May 2026) (12). The Python package publishes from GitHub Actions with attestations, per the 1 October check (10).

Soundverse API 11

Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Google Lyria and MusicGPT listings read it; the 1 October note read the tool lines (0 + 0 + 3 + 0 + 0 = 3). No dated release, changelog entry or model launch date was found for the API; the docs' "What changed" section on the move to POST /v1/generations is undated (0 of 30). No deprecation policy or dated notice. Old versioned routes still work through a compatibility layer, and the docs say integrators "don't need to rewrite anything yet" with no date (0 of 12). No model was removed between the 1 October and 5 November readings, and song models v5, v6 and v7, music, singing, stems and SFX are all still priced (8 of 8). No public changelog (0 of 15). Support through the help centre and a contact page, with no stated response time (3 of 10). No official SDK (0 of 15) and so no stated runtimes (0 of 10). 0 + 0 + 8 + 0 + 3 + 0 + 0 = 11.

Reliability fal music models +50

fal music models 77

Graded as a hosted service on the queue API. Instatus page at status.fal.ai with components for Model API, Serverless API, Official Models and the dashboards, and monthly uptime figures (20). The notice history, re-read on 1 November 2026 for June to November, has two notices in the 90 days from 3 August, a 30-minute major outage of synchronous calls to fal.run on 4 September (the queue wasn't named, so partial) and 18 minutes of degraded performance on 29 September, and none in August or October (20). Concurrency is published, 2 for a new account rising to 40 self-serve with paid invoices over four weeks, and queued requests are never rejected (15). A 429 carries type concurrent_requests_limit and X-Fal-needs-retry: 1, the docs give backoff of 1, 2, 4 and 8 seconds, the queue requeues with no maximum and the SDK retries run() up to 10 times, and failed requests and queue time aren't charged. There is no idempotency key, so the line reads 12 as on fal's video listing (12). No SLA document is published for self-serve (0). The queue API is generally available (10).

Soundverse API 27

No status page found; the platform header shows only an API health indicator (0). No readable incident history (5). Limits are enforced per tool and per model, per hour and per day, and no numbers are published (0). The docs document a 429 RateLimited error with retryable: true and no Retry-After or rate-limit headers, and say to back off and retry with the same Idempotency-Key, which returns the original task without billing again on every create call. The idempotency key covers the billed create, but "back off and retry" states no wait time or backoff schedule, and this run holds an untimed retry instruction at the earlier partial, as for the StepFun and Harmony listings (12, the 1 October split of 5 + 7). No SLA (0). The Enterprise API isn't labelled beta (10). Re-read on 5 November. 0 + 5 + 0 + 12 + 0 + 10 = 27.

Security & auth fal music models +48

fal music models 73

Keys take one of seven permission presets (API, SERVERLESS, DEPLOY, COMPUTE, BILLING, READONLY, FULL) or a custom permission list, can be limited to named models and can expire after 1 hour to 1 year, since 9 October 2026. Legacy ADMIN and API keys still work (30). A READONLY preset grants no write access and a model limit narrows a key to the music endpoints it calls. Music calls have no destructive actions, and there's no approval step before a paid generation (15). Returns generated audio and fal's own catalogue text (10). Usage and billing per request through the platform APIs (10). https://fal.ai/.well-known/security.txt and /security.txt returned 404 on 1 November 2026 and no disclosure policy or bug bounty was found. The enterprise page mentions SOC 2 and the DPA of 31 July 2026 has a data security exhibit, but the trust centre at trust.fal.ai renders only in a browser, so the report and its scope were unread. Read as on fal's video listing (8).

Soundverse API 25

Model reading of the checklist (credential, training, retention, operator visibility, programme), as the Google Lyria and MusicGPT listings read it; the 1 October note read the tool lines (20 + 0 + 10 + 5 + 0 = 35). Plain bearer keys with an sksoundverse_ prefix from the self-serve platform, which can be revoked, with no scopes, expiry or rotation documented (20 of 30). No statement was found on whether API inputs or outputs train Soundverse's models. The whitepaper says training uses licensed or consented material, which doesn't say how API data is treated, and the privacy policy body is served from a path robots.txt disallows, so it couldn't be read on 5 November (0 of 20). Outputs are saved to the account's Library and hidden from public surfaces by default, with short-lived signed download URLs, and no retention period, deletion route or zero-retention option was found (0 of 15). Each generation has an ID, GET /v1/generations lists the account's tasks and GET /v1/account/balance shows the wallet, with no audit log found (5 of 15). No security.txt (404 on 5 November), disclosure policy, bug bounty or certification found (0 of 20). 20 + 0 + 0 + 5 + 0 = 25.

Transparency & trust fal music models +18

fal music models 64

Closed platform with published terms (8 September 2026) and API Services supplemental terms. The clients are MIT and the catalogue marks each model's license_type. The terms warrant nothing about rights in output, and output rights come from each upstream model's licence (13). Data handling is documented and mostly agrees. The API Services terms say fal will not use client content to train or develop its products, except on models marked Pending Enterprise Ready, request payloads are kept 30 days with an opt-out header and a delete API (per fal's video listing, 8 October), and the privacy policy of 22 July 2026 deletes account data 30 days after closure. Content sent to a third-party model goes to that third party (22). Model pages carry dated deprecation notices, Mirelo SFX endpoints on 15 December 2026 with a named replacement and other models on 22 and 25 October and 17 November, but there's no written policy, and the 17 December notice for fal-ai/elevenlabs/music read on 1 October no longer shows. Several dated notices with no policy read 12, as on fal's video listing (12). The DPA of 31 July 2026 names a subprocessor list with 15 days' notice of new subprocessors, but trust.fal.ai renders only in a browser, and the privacy policy says processing is in the United States and other countries (10).

Soundverse API 46

Closed service, and output rights are chosen per call, from royalty-free to full ownership of the master, which makes the licence for each file explicit (15). The privacy notice names Soundverse Inc. (US) and SonicLabs AI Private Limited (India), and the whitepaper says training uses only licensed or consented material, per the 30 September check; on 5 November the terms, privacy and acceptable use bodies load from /landing/, which robots.txt disallows, so they weren't re-read. Retention periods weren't found (10). Older versioned routes still work through a compatibility layer, but there are no dated deprecation notices (5). No subprocessor list or data locations found (0). 15 + 10 + 5 + 0 = 30.

Schema & documentation fal music models +14

fal music models 89

An OpenAPI 3.1 document for the queue API, and a per-endpoint OpenAPI 3.1 document from the catalogue API with expand=openapi-3.0, read for fal-ai/lyria2, beatoven/music-generation and mureka/v9.5/generate/song on 1 November 2026 (25). The 1 October reading of per-endpoint documents on fal.ai's ?endpoint_id= path is struck, because fal.ai's robots.txt disallows that query. A docs llms.txt and an llms.txt per model with schema, defaults and price (10). Model pages say what each model is for, but rarely when not to use it (12). Inputs are typed per model, with enums such as output_format and ranges such as Beatoven's duration from 5 to 150, but Mureka's rule that one of lyrics or prompt is needed sits in prose (13). Code examples on every model page, a model error reference with typed errors including audio_duration_too_long and unsupported_audio_format, and the concurrency 429 documented (14). Versioned endpoint IDs (elevenlabs/music/v2.5) and a dated public changelog (15).

Soundverse API 75

An OpenAPI document on the help site, still listed under "OpenAPI Specs" in help.soundverse.ai/llms.txt on 5 November; the file itself is per the 30 September check, not re-read on 5 November (25). llms.txt on the help site, with a Markdown copy of each page (10). The docs explain the single generations endpoint, the compat routes and the async flow, and a tool catalogue lists each operation with its price, with little on when to pick one tool_id over another (12). license is an integer from 0 to 5 that defaults to royalty-free, and the native route takes payload_json, a JSON-encoded string of the tool's own fields, which is looser than a typed field per capability (9). A structured error model with named errors (RateLimited, InsufficientFunds, InvalidGenerationInput, DependencyUnavailable, UNAUTHENTICATED, INVALID_API_KEY) and a retryable flag (14). /v1 routes plus a compatibility layer for older versioned routes, and no changelog (5). 25 + 10 + 12 + 9 + 14 + 5 = 75.

Agent ergonomics fal music models +11

fal music models 83

Results are small JSON with a file URL, and a model's llms.txt is loaded on demand (15). Length and format controls depend on the model, Lyria 2 is fixed at 30-second clips while MiniMax, ElevenLabs and Mureka take a duration (5). Queue status, webhooks and a catalogue API with limit, category and a cursor (20). Errors carry a machine-readable type, the docs say which to retry and X-Fal-Needs-Retry marks retryable failures, read the same way as fal's video listing (18). Failed requests and queue time aren't charged and the clients retry, but there's no idempotency key, so a repeated submit is a second billable job (10). Most music models need only a prompt (7), official Python and JavaScript clients (8).

Soundverse API 72

Creates return a small JSON task at once and outputs arrive as file IDs, but song length isn't a documented parameter and downloads take a second call (15). GET /v1/generations lists tasks with cursor pagination, plus polling and an SSE progress stream on /v1/generations/{id}/stream with a resume cursor (10). Errors name the cause and say whether to retry (20). Idempotency-Key on creates returns the original task without billing again (20). The licence defaults to royalty-free and one endpoint covers every capability (7), with no official SDK (0). Re-read on 5 November. 15 + 10 + 20 + 20 + 7 = 72.

Score by category

CategoryWeightfal music modelsSoundverse APIEdge
Reliability16%7727fal music models +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8975fal music models +14
Agent ergonomics13%8372fal music models +11
Security & auth14%7325fal music models +48
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8211fal music models +71
Transparency & trust7%6446fal music models +18
Negative events≤1500
TotalBB 72.6/100E 42.4/100

Facts side by side

Factfal music modelsSoundverse API
KindPlatformModel API
Vendorfal (Features & Labels, Inc.)Soundverse Inc.
Hosted endpointhttps://queue.fal.runhttps://apiv2.soundverse.ai/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
Price for music generation$0.15 per call$0.07 per call
x402nono
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-29none
Terms last updated2026-09-08couldn't be read
Privacy policy last updated2026-07-22couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity186 stars, 1.7M npm/wk, 825k PyPI/wknone
Agent reviews4/5 (2)4/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

fal music models

One key and one queue API reach 30 active music endpoints from Google, ElevenLabs, MiniMax, Mureka, Stability and open-weights models, each with a published price and OpenAPI document, and keys can be limited by permission, model and expiry. Billing units differ per model, there is no free tier, and a person must sign up and buy credit.

Soundverse API

Songs with vocals, instrumentals, stems (2, 6 or 12), SFX, voice cloning and remix behind one endpoint, priced per call by licence tier, with idempotent creates and retry flags on errors. No status page, changelog, rate-limit numbers or security.txt.

Before you call either

fal music models

  1. Submit to queue.fal.run and poll or use a webhook. Synchronous fal.run calls went down for 30 minutes on 2026-09-04
  2. Check the unit on the model page. ElevenLabs v2.5 bills a whole minute for a 30-second clip, and Mureka 9.5 costs $0.50 without lyrics
  3. Pin the versioned endpoint, for example fal-ai/elevenlabs/music/v2.5
  4. Give agents an API preset key limited to the music models they call, with an expiry, never a FULL or legacy ADMIN key
  5. For stems, run fal-ai/demucs on the output

Soundverse API

  1. Always set Idempotency-Key on creates, so a retry after a 429 doesn't bill twice
  2. Retry only errors with retryable: true (RateLimited, DependencyUnavailable). 401, 403 and 404 won't fix themselves
  3. Pass license explicitly. The default is 1, royalty-free, which doesn't cover sync or distribution
  4. Expect a job_id from every create, compat routes included, then poll GET /v1/generations/{id} or open /stream, and fetch audio through GET /v1/files/{file_id}/download

Questions

Which is better for AI agents, fal music models or Soundverse API?

fal music models scores 72.6 (BB) on agent readiness against Soundverse API's 42.4 (E), and leads in 6 of 7 scored categories.

Which is cheaper for music generation, fal music models or Soundverse API?

Soundverse API, at $0.07 per call against $0.15 per call for fal music models. These are the vendors' published prices for the job.

Can an agent call fal music models and Soundverse API without installing anything?

Yes. fal music models has a hosted endpoint at https://queue.fal.run and Soundverse API at https://apiv2.soundverse.ai/v1.

Other comparisons with fal music models or Soundverse 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.