MusicGen on Replicate by Replicate (Cloudflare)

# Fix list: MusicGen on Replicate

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/replicate-musicgen, the October 2026 research run, assessed 1 October 2026. Grade C, 54.4 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on MusicGen on Replicate: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Security & auth, 40 out of 100, up to 10.5 more on the total

Why it scored 40: Plain bearer account tokens, no scopes found (20). No read-only or least-privilege mode found, and monthly spend limits were removed in July 2025 (0). MusicGen returns audio, no untrusted content (10). Every prediction is listed with inputs, logs and timing in the dashboard and API (10). No security.txt and no Replicate disclosure policy or certification found, and we didn't confirm whether Cloudflare's programme covers Replicate (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 2. Reliability, 48 out of 100, up to 10.4 more on the total

Why it scored 48: replicatestatus.com exists, but in this run it showed a page last updated in April and old incidents, while the listing found it redirecting to Cloudflare's status page. Either way we couldn't read a current history (10 and 5). Rate limits published, 600 prediction creates a minute and 3,000 a minute on other endpoints, with 6 a minute for accounts without a payment method (15). A 429 says "Your rate limit resets in ~30s", which gives an agent a wait time (8), but there's no idempotency key or safe-retry guidance for predictions (0). No SLA for self-serve (0). The predictions API is generally available (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 3. Payments & pricing, 20 out of 100, up to 10 more on the total

Why it scored 20: No x402, MPP or L402 on Replicate's API (0). GPU prices per second ($0.0014 on an A100 80GB for MusicGen, about $0.035 a run) and official-model prices per output are published without a login (20). No free tier. Accounts without a payment method are held to 6 requests a minute, and we found no free credit offer (0). A person signs up and adds billing (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 4. Maintenance & community, 32 out of 100, up to 6 more on the total

Why it scored 32: The MusicGen version dates from 2024-03-28. The latest platform changelog entry is 2026-04-21, 163 days before this check, and we scored that (10). No changelog entries in the last 90 days (0). Public changelog and support, but we didn't check how quickly Meta answers audiocraft issues or Replicate answers support (10). Official Python and JavaScript clients and an MCP server, but the npm client was last published as 1.4.0 on 2025-11-17 (12). Client CI not checked (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 5. Agent ergonomics, 75 out of 100, up to 4.1 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 6. Transparency & trust, 70 out of 100, up to 2.6 more on the total

Made of editorial 50, provenance 90.

Why it scored 70: 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. The docs don't say whether prediction data trains anything (20). No deprecation policy or dated notices for this model found (5). Subprocessors and data locations not checked (5).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- security.txt: not found (0 of 10)

## 7. Schema & documentation, 87 out of 100, up to 2.1 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- We couldn't read the MusicGen model page or the Cloudflare status history on 2026-10-01, so the run count, the 2024-03-28 version date and the GPU price rest on the listing's check of 2026-09-30.
- Whether Cloudflare's security programme and certifications now cover Replicate.
- Whether failed predictions bill GPU time.

## Weaknesses

- MusicGen weights are CC-BY-NC 4.0, so no commercial use
- Instrumental only, and the model version dates from 2024-03-28
- No API token scopes and no security.txt
- No platform changelog entries since 2026-04-21, and the npm client is from 2025-11-17

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

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

## What the review panel asked for

- Idempotency key on predictions
- State failed-run billing

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.