Head to head · Music generation · October 2026 research run

Loudly Music API vs Soundverse API

Soundverse API scores 42.4 (E) on agent readiness against Loudly Music API's 37.5 (F), and leads in 4 of 7 scored categories. Loudly Music API leads on payments & pricing. Both do music generation.

Best music generation for AI agents · All 66 music comparisons

Which one, for what

Loudly Music API F

Best for Apps that need instrumental tracks with stems, remix and mastering from one vendor under a royalty-free licence, and that can start on a free allowance.

Ahead on

  • Payments & pricing, 45 against 30

Watch for

No status page, changelog, rate limits or 429 guidance

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.

Ahead on

  • Reliability, 27 against 15
  • Agent ergonomics, 72 against 51
  • Maintenance & community, 11 against 3

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

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.

Agent ergonomics Soundverse API +21

Loudly Music API 51

Responses are JSON with track URLs (15) and duration is a parameter, but we found no output format choice in the spec (5). List endpoints take page and limit and return page metadata (10). Error payloads name the cause, including 402 for credits and 403 when the Manta flag is off, with no 429 documented (15). No idempotency key or retry guidance, and test=true helps wiring but not retries (0). Genre, BPM and instrument values must match the genres endpoint, and requests are multipart form data (6). No official SDK (0). Per the 1 October check, not re-read on 10 November because Loudly's terms bar automated access to the Service. Total 51.

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.

Payments & pricing Loudly Music API +15

Loudly Music API 45

No x402, MPP or L402 (0). The developer pricing page lists subscription tiers from $0.15 a track at 500 tracks a month to $0.071 at 50,000, while the pay-as-you-go per-track price shows only after sign-in. That page didn't render for us on 2026-10-01, so this relies on the listing's check of 2026-09-30 (10). A new key comes with a free track allowance on sign-up, with no card step described, and test=true calls are free (20). A person signs up on the developer portal (0). Per the 1 October check, not re-read on 10 November because Loudly's terms bar automated access to the Service. Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Soundverse API 30

No x402, MPP or L402 in the docs or pricing (0). Per-call USD prices by capability and licence tier on the public pricing page and tool catalogue, re-read on 5 November (20). No free tier published, and plans need a sign-in to view (0). A person signs up and funds a wallet (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Soundverse API +12

Loudly Music API 15

No status page found (0). No readable incident history (5). No rate limits with numbers, only a note that paid plans get higher limits (0). The OpenAPI spec documents 402 for insufficient credits but no 429, Retry-After or backoff guidance (0). No SLA (0). The API is versioned 1.0.0 and isn't labelled beta (10). Per the 1 October check, not re-read on 10 November because Loudly's terms bar automated access to the Service. Total 15.

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.

Maintenance & community Soundverse API +8

Loudly Music API 3

Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Mubert, Soundverse and Google Lyria listings read it; the 1 October note read the tool lines (0 + 0 + 3 + 0 + 0 = 3). No dated release, model launch or API change was found; the terms' 21 January 2026 date isn't an API change (0 of 30). No deprecation policy or dated notice (0 of 12). The spec couldn't be re-read on 10 November, so whether a model was removed since 1 October is unchecked (0 of 8). No public changelog (0 of 15). Support is help@loudly.com, with no stated response time (3 of 10). No official SDK (0 of 15) and so no stated runtimes (0 of 10). 0 + 0 + 0 + 0 + 3 + 0 + 0 = 3.

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.

Score by category

CategoryWeightLoudly Music APISoundverse APIEdge
Reliability16%1527Soundverse API +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7575even
Agent ergonomics13%5172Soundverse API +21
Security & auth14%2525even
Payments & pricing10%4530Loudly Music API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%311Soundverse API +8
Transparency & trust7%4346Soundverse API +3
Negative events≤1500
TotalF 37.5/100E 42.4/100

Facts side by side

FactLoudly Music APISoundverse API
KindModel APIModel API
VendorLoudly GmbHSoundverse Inc.
Hosted endpointhttps://soundtracks.loudly.com/apihttps://apiv2.soundverse.ai/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
Price for music generationnot published$0.07 per call
x402nono
Read-only variant documentednono
llms.txtyesyes
Terms last updatedno date givencouldn't be read
Privacy policy last updatedcouldn't be readcouldn't be read
Customer content may train modelsyescouldn'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 waivernot found in the textcouldn't be read
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Soundverse 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

Loudly Music API

Loudly's API generates instrumental tracks with its VEGA models and vocal songs through MANTA-1, with stems, remix and mastering, under a public OpenAPI spec with error schemas. There is no status page, changelog, rate limit or 429 guidance, and the terms let Loudly train on uploaded audio and send MANTA-1 inputs to Mureka.

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

Loudly Music API

  1. Send test=true while wiring up. It returns a dummy song and spends no credits
  2. Call GET /api/ai/genres first. Genre, BPM range and instrument names must match that list
  3. Treat 402 as out of credits and stop, not retry
  4. A 403 on Manta routes means the account flag is off, not a bad key
  5. Don't upload audio you can't license to Loudly for training; the terms grant it for uploads

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, Loudly Music API or Soundverse API?

Soundverse API scores 42.4 (E) on agent readiness against Loudly Music API's 37.5 (F), and leads in 4 of 7 scored categories. Loudly Music API leads on payments & pricing.

Do Loudly Music API and Soundverse API need an API key?

Both need an API key.

Can an agent call Loudly Music API and Soundverse API without installing anything?

Yes. Loudly Music API has a hosted endpoint at https://soundtracks.loudly.com/api and Soundverse API at https://apiv2.soundverse.ai/v1.

Other comparisons with Loudly Music API 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.