Head to head · Music generation · October 2026 research run

Mubert API vs MusicGen on Replicate

MusicGen on Replicate scores 67.3 (B) on agent readiness against Mubert API's 36.9 (F), and leads in every scored category. Both do music generation.

Best music generation for AI agents · All 66 music comparisons

Which one, for what

Mubert API F

Best for Apps that hand background music to many end users, or need endless streams and fixed-cost quotas.

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

Watch for

Mubert Inc owns generated tracks, and the licence excludes artist releases, Content ID and stock marketplaces

MusicGen on Replicate B

Best for Cheap prototypes, research and melody-conditioned experiments where non-commercial output is acceptable, and for teams already on Replicate who can switch to its commercial music models.

Ahead on

  • Reliability, 75 against 30
  • Schema & documentation, 87 against 69
  • Agent ergonomics, 75 against 42
  • Security & auth, 40 against 25
  • Payments & pricing, 45 against 15
  • Maintenance & community, 75 against 31
  • Transparency & trust, 78 against 45

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

MusicGen weights are CC-BY-NC 4.0, so no commercial use

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 MusicGen on Replicate +45

Mubert API 30

No status page found (0). No readable incident history (5). Quotas published with numbers, monthly generations and streaming minutes per plan (100, 5,000 and 30,000) plus per-customer daily caps and concurrency in the licence object (15). No 429 or retry guidance in the docs, re-read on 10 November (0). No SLA (0). API v3 isn't labelled beta (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.

MusicGen on Replicate 75

Graded as a hosted service, on the predictions API. Replicate is part of Cloudflare, and replicatestatus.com redirects to Cloudflare's status page filtered to Replicate, where a Replicate component carries 30 and 90-day history (20). Read on 4 November, the component shows 5 days with incidents in 90 days, all in September 2026, and none in the last 30 days. They cover third-party models that couldn't scale out (14 and 15 September), a Pruna-specific issue (17 September), intermittent 500s from backend services (24 September) and stuck hot-swapped Flux models (28 September). Each names a subset of models or intermittent errors, so each reads as partial, minor only, as for Replicate's deployments and video listings (20). 600 prediction creates a minute, 3,000 a minute on other endpoints, and 6 a minute for granted credit without a payment method, re-read on 4 November (15). A 429 body says "Your rate limit resets in ~30s" and the error-code page gives retry advice per code, but there's no Retry-After header or idempotency guidance (10 of 15, read as on the deployments listing). The terms disclaim service levels and no SLA was found (0). The predictions API is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Maintenance & community MusicGen on Replicate +44

Mubert API 31

Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Soundverse, MusicGPT and Google Lyria listings read it; the 1 October note read the tool lines (30 + 0 + 3 + 15 + 0 = 48), with recency and the registry line resting on the MCP registry's v0.1 search, which this run no longer reads. The newest dated API change found is the vendor's skills repository adding the Music MCP skill on 15 September 2026, after the track edit and similar-track endpoints on 13 August, 56 days before this check (20 of 30). The 27 October date on llms.txt records no change. No deprecation policy or dated notice (0 of 12). No mode, format or duration was removed between the 1 October and 10 November readings (8 of 8). No public API changelog; the What's New page covers Mubert Render (0 of 15). Support by email at business@mubert.com, with no stated response time and no community channel found (3 of 10). No official SDK, only the agent skills and the MCP server (0 of 15), and so no stated runtimes (0 of 10). 20 + 0 + 8 + 0 + 3 + 0 + 0 = 31.

MusicGen on Replicate 75

MusicGen's newest version is still from 28 March 2024 and the platform changelog's newest entry is 21 April 2026. Every dated source of the vendor's own counts. Cog, Replicate's own CLI and model server, tagged v0.23.1 on 19 October 2026, a behaviour fix (predictions fail when output uploads fail), counted in full as on Replicate's deployments and video listings (30). Cog tagged v0.22.0 on 13 August, v0.23.0 on 22 September and v0.23.1 on 19 October, three releases in the 90 days from 6 August (20). Public changelog and support; Meta's audiocraft and Replicate's support response times weren't read (10 of 25). Official Python, JavaScript and MCP packages exist, but the stable client releases are JavaScript 1.4.0 (17 November 2025) and Python 1.0.7 (27 May 2025), with the Python repository's newest tag 1.1.0b3 (26 August 2025), the same evidence as on 1 October, so the earlier 12 stays; the official MCP registry wasn't read, since this run doesn't call its API (12). Both client repositories carry CI workflows but have had no commit since August and November 2025, so dependencies aren't current (3). 30 + 20 + 10 + 12 + 3 = 75.

Agent ergonomics MusicGen on Replicate +33

Mubert API 42

21 MCP tools, in the 11 to 30 band. The docs say nine only read and spend nothing, with no toolset or read-only subset to load on its own (15). Webhooks for generation status from the Startup plan, and a library search to try before generating, which the Trial plan doesn't include (15). No error codes or messages documented (0). No idempotency key. The quota check before spending rests on the listing's check of 30 September, a held partial (5). Sensible defaults and pre-rendered durations, no SDK beyond an agent skill and the MCP server (7). 15 + 15 + 0 + 5 + 7 = 42.

MusicGen on Replicate 75

Prediction JSON returns an output URL (15), and the caller sets duration and format (10). Paginated prediction lists, webhooks with event filters, and Prefer: wait for short runs (20). The 429 message carries a reset time and failed predictions return an error field (15). No idempotency key found, and GPU-time billing means a retried run is a second bill (0). Every MusicGen input has a default, duration 8 seconds (7), official Python and JavaScript clients (8).

Transparency & trust MusicGen on Replicate +33

Mubert API 45

Closed service. The terms and llms.txt say plainly that Mubert Inc owns generated music and grants a licence to use it, and list where it can't go (artist releases on Spotify or Apple Music, Content ID, stock marketplaces) (15). The privacy policy, read on 10 November, is undated and covers the website, deferring the API to separate agreements that weren't found. It keeps profile data 'as long as it is necessary', says data is shared with no third party while naming Stripe, third-party form services and interest-based ads (5 of 30). No deprecation policy or dated notices found (0). No subprocessor list or data locations found, and the terms and privacy policy give a San Francisco address while the footer, llms.txt and the registered office give Dover, Delaware (0). 15 + 5 + 0 + 0 = 20.

MusicGen on Replicate 78

MusicGen code is MIT and the weights are CC-BY-NC 4.0, so the licence is clear and rules out commercial output. Replicate's own terms name Replicate, LLC (20). API prediction inputs, outputs, files and logs are deleted after an hour by default, while web predictions are kept indefinitely, re-read on 4 November. The docs don't say whether prediction data trains anything (20). No written deprecation policy and no dated notice for this model, but the platform changelog dates deprecations such as the monthly spend limit (1 July 2025), read as on Replicate's deployments and video listings (12). A subprocessor page lists 17 companies with their purpose, each located in the United States (15). 20 + 20 + 12 + 15 = 67.

Payments & pricing MusicGen on Replicate +30

Mubert API 15

No x402, MPP or L402 on the API or MCP server (0). Plan prices are public, $49, $199 and $499 a month, with no per-call price (10). No free API tier; the $49 plan is now called Trial and is a paid plan. The free tier mentioned in llms.txt is for Mubert Render, not the API (0). Credentials arrive by email after a checkout (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

MusicGen on Replicate 45

No x402, MPP or L402 on Replicate's API (0). GPU prices per second ($0.0014 on an A100 80GB for MusicGen, which the model page now puts at about $0.041 a run, 24 runs per $1) and official-model prices per output are published without a login (20). No standing free tier, but an account granted credit can run predictions without a payment method at up to 6 a minute, read as on Replicate's deployments listing (10 of 20). A person signs up and adds billing (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Schema & documentation MusicGen on Replicate +18

Mubert API 69

OpenAPI document for v3 at music-api.mubert.com, linked from llms.txt as the OpenAPI specification and from the docs' Swagger section, read on 30 September and not re-fetched, plus a hosted MCP server (25). llms.txt (10). The docs explain the licence, customer and track flows, group the 21 MCP tools by whether they spend quota, and say when a pre-rendered duration returns in one request. The MCP tool descriptions themselves weren't read (12). Typed inputs with a fixed list of pre-rendered durations (5 to 300 seconds), intensity, mode and format enums and a playlist_index (12). Request and response examples, but only 200 and 204 documented, no error codes (5). Versioned /api/v3 path, no changelog (5). 25 + 10 + 12 + 12 + 5 + 5 = 69.

MusicGen on Replicate 87

Public OpenAPI document for the HTTP API and a typed input schema per model version (25). llms.txt (10). The model page says what MusicGen does and that its weights are non-commercial, but little on when to use melody conditioning against plain text (12). Typed inputs with enums for model_version, output_format and normalization_strategy and an integer duration (13). Examples in several languages, prediction status and error fields documented (12). Model versions pinned by hash and a dated platform changelog (15).

Score by category

CategoryWeightMubert APIMusicGen on ReplicateEdge
Reliability16%3075MusicGen on Replicate +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6987MusicGen on Replicate +18
Agent ergonomics13%4275MusicGen on Replicate +33
Security & auth14%2540MusicGen on Replicate +15
Payments & pricing10%1545MusicGen on Replicate +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3175MusicGen on Replicate +44
Transparency & trust7%4578MusicGen on Replicate +33
Negative events≤1500
TotalF 36.9/100B 67.3/100

Facts side by side

FactMubert APIMusicGen on Replicate
KindModel APIPlatform
VendorMubertReplicate (Cloudflare)
Hosted endpointhttps://music-api.mubert.com/api/v3https://api.replicate.com/v1
TransportsHTTP, Streamable HTTPHTTP, stdio, SSE (legacy)
AuthOAuth or keyAPI key
PricingPaidPay per use
Price for music generationnot published$0.498 per minute of audio
x402nono
LicencenoneMIT code, CC-BY-NC-4.0 weights
Tools exposed21none
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.mubert/musicnot listed
Last release2026-09-152024-03-28
Terms last updatedno date given2026-04-01
Privacy policy last updatedno date given2026-04-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity0 stars24k stars, 634k npm/wk, 387k PyPI/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates MusicGen on Replicate 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

Mubert API

Hosted MCP server with 21 tools and OAuth 2.1 with PKCE, beside a REST API v3 with a linked OpenAPI file. Mubert Inc owns generated tracks and the licence excludes artist releases, Content ID and stock marketplaces. No free API tier, and no statement on training or retention of API data was found.

MusicGen on Replicate

About $0.041 a run, billed by GPU second on an A100, with text or melody conditioning and published rate limits. MusicGen weights are CC-BY-NC 4.0, so no commercial use, and the newest model version dates from March 2024.

Before you call either

Mubert API

  1. Search the library before generating on Startup plans and above. A match costs no generation, and the Trial plan has no curated library
  2. Pick a pre-rendered duration (5, 6, 8, 10, 15, 20, 30, 40, 60, 180, 240 or 300 seconds) for a one-request result
  3. Download tracks straight away. URLs expire after 900 seconds by default
  4. Treat stream URLs as secrets. They carry the customer access token

MusicGen on Replicate

  1. Set duration (default 8 seconds) and model_version. The default is stereo-melody-large
  2. Use Prefer: wait for short clips and webhooks for long ones
  3. On a 429, wait the reset time in the message, about 30 seconds
  4. Switch to google/lyria-2 or minimax/music-2.5 when output must be commercial
  5. Add a payment method first, or you're held to 6 requests a minute

Questions

Which is better for AI agents, Mubert API or MusicGen on Replicate?

MusicGen on Replicate scores 67.3 (B) on agent readiness against Mubert API's 36.9 (F), and leads in every scored category.

Can an agent call Mubert API and MusicGen on Replicate without installing anything?

Yes. Mubert API has a hosted endpoint at https://music-api.mubert.com/api/v3 and MusicGen on Replicate at https://api.replicate.com/v1.

Other comparisons with Mubert API or MusicGen on Replicate

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.