MusicGPT API vs Soundverse API

MusicGPT API

A public OpenAPI 3.1 file with 27 operations, llms.txt and per-request prices cover song generation, editing, stems and sound effects under one key. No status page, SLA, security.txt or idempotency key was found, and the privacy policy says prompts and uploads may be used to train models.

Soundverse API

Songs with vocals, instrumentals, stems (2, 6 or 12), SFX and remix behind one endpoint. No status page, changelog or security.txt.

MusicGPT API

1. Send the key as the raw Authorization header value. The docs show no Bearer prefix
2. Budget two songs for each music request. POST /v2/MusicAI returns two versions and the price is per song
3. Save task_id and poll GET /v1/byId with conversionType, or set webhook_url. Music AI V2 sends up to seven webhooks a request
4. Pass model explicitly. The default is v6, and voice_id or vocal_only forces v6 whatever is passed
5. Do not retry a create blindly after a timeout. No idempotency key is documented, so a retry may bill again

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 and 403 won't fix themselves
3. Pass license explicitly. The default is 1, royalty-free, which doesn't cover sync or distribution
4. Fetch audio through GET /v1/files/{file_id}/download, then poll GET /v1/generations/{id} or open /stream for progress