Spotify's AI Persona badge: labeling an AI music video channel
Spotify will badge AI Persona profiles and skip them in recommendations. What a video channel with generated audio should label and keep.

What is Spotify's AI Persona badge? Per TechCrunch's August 11, 2026 report (read 2026-10-04), Spotify will put an AI Persona label on artist profiles whose names and imagery may be generated and do not represent real people, and exclude those profiles from recommendations by default. Their music stays available and is served in editorial and algorithmic surfaces only if a listener follows the artist. The badge was reported to start appearing in mid-September.
The label targets fake artists, not background music in videos. If your channel publishes video with a generated bed and never invents an artist, the badge is not about you. If you build a persona with a made-up name and face for a release, it is.
Who the badge is aimed at
Read the report on TechCrunch. The trigger is a profile that does not represent a real person, not the use of AI tools by a real artist. That is a narrower category than all AI music, and the report frames it that way.
A decision table for a video channel
| Case | Likely badge target? | Safe habit |
|---|---|---|
| Video with a generated instrumental bed | No, no artist profile involved | Keep the cue in your project notes |
| Release under a made-up artist name and face | Yes, profile may not represent a real person | Disclose or use a real artist identity |
| Real artist using AI tools in a track | Reported as not the target | Keep the human work visible |
What Sume gives you for the notes
Each Music Router job echoes the requested id in job.model and names the engine in job.request.routed_model. Pair that with the metadata field on the request, which the docs say is stored on the job and not sent to the provider, so you can tag every cue with a project and a purpose.
curl -X POST https://api.sume.com/v1/music-router/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: persona-notes-001" \
-d '{"model":"sume/music-auto","prompt":"Calm piano bed, 70 BPM, A minor. Instrumental, no vocals. A 30-second track.","metadata":{"project":"channel-intro","use":"video-bed"}}'What to avoid
Do not read this as Spotify guidance on video beds. Spotify's rule concerns artist profiles on its service, and its own newsroom is the place to check any change.
Sources
Related posts
More in Use cases
- Spotify video podcast bitrate: 25 Mbit/s at 1080p, 35 at 4K
Spotify video podcasts: 25 Mbit/s CBR for 1080p, 35 for 4K, 16:9, under 10 GB and 4 hours recommended. Sume Timeline assembles up to 1800 s of audio per render.
- Square 1:1 video from Gemini Omni: it only makes 16:9 or 9:16
Omni outputs 16:9 or 9:16 only. For a 1:1 square feed post, render a Sume Timeline at 1080x1080 with fit cover or blur; the render is $0.10 per output minute.
- Substitute-day intro clip: a 20-second avatar per class period
Leave a 20-second talking-avatar instruction clip for each class period on a substitute day. $3.68 per clip at Sume's Standard rate, 720p, 4 to 60 seconds.
- Suno terms: no copyright warranty, what to tell a client
Suno assigns its rights in Pro and Premier outputs but does not warrant copyright will vest in AI output. What to write into a client brief or ad contract.
Written by Sume