Spotify AI Persona badge: does it apply to AI instrumentals?
Spotify's AI Persona badge is about an artist identity that may be AI-generated. What the announcement says, and what a Sume music job actually returns.

Spotify's AI Persona badge is defined by an artist's identity: it signals that "an artist's identity may be AI-generated and does not represent a real person." The announcement describes profiles and artist identities, not a music tool, so a track from a Sume music job is not labeled by Sume; whether a profile is an AI Persona is decided on Spotify's side.
Sume facts below come from the Music Router docs, read 2026-09-30; Spotify facts come from its newsroom post of 2026-08-11.
What does the Spotify announcement say?
The post gives a short list of behaviors. Nothing in the text we read mentions instrumentals or a specific generation tool.
| Item | What the page says |
|---|---|
| Meaning | "an artist's identity may be AI-generated and does not represent a real person" |
| Where it shows | Artist profiles (banner and About section), Search, and track rows across playlists, from mid-September |
| Self-disclosure | Artists can share AI Persona status through Spotify for Artists |
| Review | Artists are "notified and given the opportunity to self-disclose or appeal" |
| Recommendations | AI Personas are not included in editorial or algorithmic recommendations unless a listener follows them |
What does a Sume music job return?
A Music Router job returns an audio artifact on media.sume.com in result.artifacts[] with type audio. The documented result shape lists no artist profile, persona or credit fields; result.lyrics holds model-reported lyrics or a section map when present. Music is generated from POST /v1/music-router/generate, and a prompt can ask for an instrumental with the clause "Instrumental, no vocals."
The Music Router docs describe the file and its price ($0.125 per accepted generation on Music 1.0) and say nothing about distribution.
What should I check before uploading a track?
Read Spotify's own page for your case. If you present a synthetic performer as a person, that is the identity situation the badge describes; a plain instrumental release under your own name is not something the announcement addresses. Sume's docs do not cover streaming-platform rules, so this is a question for the platform and your distributor.
Keep the job id and the Sume artifact URL with your release notes so you can show how the audio was made.
How do I submit the job and fetch the track?
A music request takes mode async, sync, subscribe or webhook. With sync or subscribe, wait_timeout_seconds is 0 to 30; with webhook, webhook_url must be a public HTTPS callback. Send an Idempotency-Key on the submit, then poll GET /v1/jobs/{job_id}/status and read GET /v1/jobs/{job_id}/result. The audio is the entry in result.artifacts[] where type is audio, hosted on media.sume.com; raw provider URLs are not public outputs. The docs list no persona or credit metadata on the result; keep your own record of the job id.
The prompt is 1 to 5000 characters. Put exclusions in the positive prompt ("Instrumental, no vocals"), because a non-empty negative_prompt is refused. Full field list: Music Router docs.
Sources
Related posts
More in Use cases
- Squarespace video background on mobile: make it 16:9
Squarespace says to use landscape video like 16:9 to minimize cropping. Turn a vertical clip into 16:9 with Timeline blur fit, or crop it with Video filter.
- Squarespace background video blurry: 1080p and 3 Mbps
Squarespace advises 1080p and at least 3 Mbps for background videos. Sume sets size and fps on its renders but has no bitrate field. What to control.
- Squarespace background video not working on mobile: fallback
Phones in low-battery or power-saving mode won't play Squarespace background videos. Add a fallback image; pull a still from the clip with Video frames.
- Squarespace background video size: 60 seconds, aim for 40
Squarespace caps an uploaded section background video at 60 seconds and advises under 40. Cut a longer clip to 40 seconds with Sume Video trim first.
Written by Sume