Soundverse API vs Suno MCP

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). Polling plus an SSE progress stream on /v1/generations/{id}/stream (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), no official SDK (0).

Suno MCP 14

Tool count and definition size couldn't be read without signing in, so context cost scores as not found (0 of 25). The library:search scope shows library search exists, with no paging or size controls documented (5 of 20). Only the 401 is documented (4 of 20). Idempotency and readOnlyHint or destructiveHint annotations couldn't be read (0 of 20). Setup needs no API key and Suno's examples are plain requests, but required parameters are unknown, and an MCP server needs no SDK (5 of 15). Total 14.

Soundverse API 3

No dated release, changelog entry or model launch date found for the API (0). No dated entries in the last 90 days (0). No public changelog. Support is through the help site (3). No official SDK (0). No package to judge (0).

Suno MCP 60

The server launched on 28 October 2026, four days before this check (30). The release notes have 13 dated entries since 3 August 2026, one of them about the MCP server (20). Public release notes, a help centre with an MCP category, a support email and a Discord server, with response times not checked (10 of 25). Not in the official MCP registry under a Suno namespace. The two Suno entries there are third-party wrappers (0 of 15). No package to judge (0 of 10). Total 60.

Soundverse API 75

OpenAPI document published on the help site (25). llms.txt on the help site (10). The docs explain the single generations endpoint and the async flow, but say little about when to pick one tool_id over another (12). The license field is an integer from 0 to 5 with a default of 1, and the capability is chosen by tool_id with a per-tool parameters object, which is looser than a typed field per capability (9). A structured error model with named errors (RateLimited, DependencyUnavailable, UNAUTHENTICATED, INVALID_API_KEY) and a retryable flag (14). /v1 routes plus a compatibility layer for older versioned routes, no changelog (5).

Suno MCP 24

Suno doesn't publish the server's tool list, and the tool definitions can be read only after signing in, which this run didn't do, so no contract is public (0 of 25). suno.com/llms.txt is Markdown written for agents but describes the app as of 29 May 2026 and says nothing about the MCP server (5 of 10). suno.com/mcp and the help article list what the server does (songs, covers, extensions, mashups, Speech, uploads, Voices, playlists, credits) without per-tool purpose or when not to call (5 of 20). Typed inputs weren't readable (0 of 15). Three example prompts on suno.com/mcp, and only the 401 with its resource metadata is documented as an error (4 of 15). Dated release notes with an entry for the launch, but no server version or MCP changelog (10 of 15). Total 24.

Soundverse API 27

No status page found (0). No readable incident history (5). Limits are enforced per tool and per model, hourly and daily, but no numbers are published (0). A 429 returns a RateLimited error with retryable: true, with no Retry-After or rate-limit headers (5), and an Idempotency-Key header makes retried creates safe (7). No SLA (0). The Enterprise API isn't labelled beta (10).

Suno MCP 13

Read with the hosted lines, because the surface an agent uses is the remote server at api.suno.com/mcp. No official status page was found, and status.suno.com doesn't resolve (0 of 20). No readable incident history (5 of 30). No rate limit is published for the server. The plan table gives generation concurrency, 4 at once in a shared queue on Free and 10 in a priority queue on Pro and Premier, with daily or monthly credits, which we count in part (8 of 15). No 429, Retry-After or backoff guidance (0 of 15). No SLA (0 of 10). The server is labelled beta, and the page asks for early access (0 of 10). Total 13.

Soundverse API 35

Plain bearer keys with an sksoundverse_ prefix from the self-serve platform dashboard, with no scopes, expiry or rotation documented (20). No least-privilege mode (0). Returns generated audio and copyright-check results, no third-party content (10). Each generation has an ID and is charged to a wallet, with no audit log found (5). No security.txt, disclosure policy, bug bounty or certification found (0).

Suno MCP 49

OAuth on Suno's own authorisation server, with authorisation code and PKCE S256, refresh tokens, a revocation endpoint, open client registration, client ID metadata documents and bearer tokens in the header only. The resource lists eight scopes and keeps spending credits in its own credits:spend scope (30 of 30). The scopes separate reading, searching, writing the library and spending, but no read-only connection, spending cap or confirmation step is documented, and the consent screen wasn't seen (6 of 20). Results come from the user's own library and Suno's generation, with lyrics and titles that may come from shared or remixed songs, and no injection guidance (8 of 15). Every song lands in the library and the credit balance can be checked, with no per-call log (5 of 15). No security.txt on suno.com or api.suno.com, and no disclosure policy, bug bounty or certification found (0 of 20). Total 49.

Soundverse API 20

No x402, MPP or L402 (0). Per-call USD prices by capability and licence tier on the platform pricing page, per the listing's check of 2026-09-30 (20). No free tier published (0). A person signs up and funds a wallet (0).

Suno MCP 32

No machine payment protocol (0 of 40). Plan prices are public, Pro $10 and Premier $30 a month, and Suno says 50 credits make about 10 songs, but there's no per-song price in money and add-on credit prices sit behind a login (10 of 20). The FAQ says the server works on every plan including Free, which gives 50 credits a day with no card (20 of 20). A person signs up in a browser and approves the connection. Clients can register themselves with the authorisation server, which earns 2 (2 of 20). Total 32.